diff options
| author |   Mike Elliott <mike.elliott@amdocs.com> | 2019-09-04 14:39:20 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2019-09-04 14:39:20 +0000 |
| commit | 43dbe38488d628c8c2a6cb28cac086b7f69042fd (patch) | |
| tree | a651607d0b213be22e13ff89145294c8200300ae /shell | |
| parent | 31fefac055d3a66decc5e401bd47ee2dd2643dbe (diff) | |
Update git submodules
* Update docs/submodules/oom.git from branch 'master'
to 9cce87c808aefa7445a4da628778a34b18e8d8c6
- Merge "Move SDC Storage to RWO"
- Move SDC Storage to RWO
Today when deploying SDC 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).
SDC PVC for ES is used only for one POD.
Thus we don't need RWX.
The other values are not used as of today but changing them to RWO seems
better if they're reused again
Change-Id: I3dabbce120a14d19499330b51e808c5725588e0c
Issue-ID: SDC-2549
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Diffstat (limited to 'shell')
0 files changed, 0 insertions, 0 deletions