summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlexis de Talhouƫt <adetalhouet89@gmail.com>2019-09-02 19:02:41 +0000
committerGerrit Code Review <gerrit@onap.org>2019-09-02 19:02:41 +0000
commit7c0dce2cf284add040dbc11cb988bdfda4d4cc6c (patch)
tree2e8c99e29dd5d883d661a0d43731e6bbe6bac7ea
parent38e7725584186fa7bbd2643bf4644e4c01cb9065 (diff)
Update git submodules
* Update docs/submodules/oom.git from branch 'master' to 9d407f480e9d40460f6f76ffc6a09f61f1d6b85e - Merge "Move Storage access to RWO" - Move Storage access to RWO Today when deploying NBI 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). MongoDb PVC is used only for one Mongo instance and it's the same for maria. Thus we don't need RWX Change-Id: I4d54cd7853778d8ba6c83551a211abe34d383382 Issue-ID: EXTAPI-305 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
m---------docs/submodules/oom.git0
1 files changed, 0 insertions, 0 deletions
diff --git a/docs/submodules/oom.git b/docs/submodules/oom.git
-Subproject aaabd14bc5a271077952648b8b97a689c3a37fc
+Subproject 9d407f480e9d40460f6f76ffc6a09f61f1d6b85