From 532145625b3f11942c3939cc2df4b5082ca56bab Mon Sep 17 00:00:00 2001 From: =?utf8?q?Alexis=20de=20Talhou=C3=ABt?= Date: Mon, 2 Sep 2019 18:59:13 +0000 Subject: [PATCH] Update git submodules * Update docs/submodules/oom.git from branch 'master' to 7d875e1af3c528030235782e76748f3abf113821 - Merge "Move CLAMP Storage access to RWO" - Move CLAMP Storage access to RWO Today when deploying CLAMP with OOM, the PersistentVolumeClaim needs the "ReadWriteMany" (or "RWX") capability. According to Kubernetes Documentation (https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes), ReadWriteMany stands for "the volume can be mounted as read-write by many nodes". That means that a particular PVC needs to be read and written from many pods. That also means that your code takes that into account and do the work to avoid write at the same place at the same time. An issue on RWX mode is that most "official" storage driver from Kubernetes doesn't support it (13 over the 19 drivers doesn't support it, espacially OpenStack, Amazon and Google storage classes). CLAMP PVC is used only for one ES instance. Thus we don't need RWX. Change-Id: I3a17195bca4f0f01b5cdb0d8e803bb2a8ab2dd38 Issue-ID: CLAMP-488 Signed-off-by: Sylvain Desbureaux --- docs/submodules/oom.git | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/submodules/oom.git b/docs/submodules/oom.git index e516c8f90..7d875e1af 160000 --- a/docs/submodules/oom.git +++ b/docs/submodules/oom.git @@ -1 +1 @@ -Subproject commit e516c8f904f2d6f67156dafcf4ace4e364c1c4ec +Subproject commit 7d875e1af3c528030235782e76748f3abf113821 -- 2.16.6