summaryrefslogtreecommitdiffstats
path: root/docs/submodules
diff options
context:
space:
mode:
authorMike Elliott <mike.elliott@amdocs.com>2019-09-05 19:39:15 +0000
committerGerrit Code Review <gerrit@onap.org>2019-09-05 19:39:15 +0000
commit9782e2f802c8a064d15c4e1567f4c14128538d3e (patch)
treebee464b05565c146272d73441e371475960f6d2e /docs/submodules
parenta542573fe1330d1ff38bd602a8dfc3e0ca9d8e3b (diff)
Update git submodules
* Update docs/submodules/oom.git from branch 'master' to ae180c725f0c0e81bad46ed93439a51d1e8b0676 - Merge "Move Modeling Storage to RWO" - Move Modeling Storage to RWO Today when deploying Policy 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). Modeling PVC for is used only for one POD. Thus we don't need RWX. Change-Id: Ic4b8f5a336f2b9edfdf25ef3cc549b389f9b6f65 Issue-ID: MODELING-213 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Diffstat (limited to 'docs/submodules')
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 8a45ff1c6b51fdc6cf5dae9c0e84899fdb341a3
+Subproject ae180c725f0c0e81bad46ed93439a51d1e8b067