summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorAlexis de Talhouƫt <adetalhouet89@gmail.com>2019-09-02 19:00:11 +0000
committerGerrit Code Review <gerrit@onap.org>2019-09-02 19:00:11 +0000
commit86a54dd8cca5ce1cf58bd1937ae497cd1c5b5229 (patch)
tree22291fe68c6a342b8f94b7df2d5507b0c7973ee7 /docs
parentcec54975013fc7a07cf45524a600337c91c31853 (diff)
Update git submodules
* Update docs/submodules/oom.git from branch 'master' to bc0abc02f0889bd4e32333a9abed152b2e98d8fb - Merge "Move Policy Storage to RWO" - Move Policy 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). Policy PVC for Nexus and Policy PVC for mariadb are used only for one POD. Thus we don't need RWX. Change-Id: Idf8a6ba8ef14ce7ca397438c2200c11517d0458e Issue-ID: POLICY-2019 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Diffstat (limited to 'docs')
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 47babc71b451f4eb88b8f149f91a035cd3865af
+Subproject bc0abc02f0889bd4e32333a9abed152b2e98d8f