diff options
| author |   Alexis de Talhouët <adetalhouet89@gmail.com> | 2019-09-02 18:59:13 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2019-09-02 18:59:13 +0000 |
| commit | 532145625b3f11942c3939cc2df4b5082ca56bab (patch) | |
| tree | 6759433d9fedfd7e0be2beae3d9901b95983b1ae /docs/index.rst | |
| parent | 8048430d3fb6b913df3d453c944d2b1ac2d0ad86 (diff) | |
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 <sylvain.desbureaux@orange.com>
Diffstat (limited to 'docs/index.rst')
0 files changed, 0 insertions, 0 deletions