diff options
| author |   Mike Elliott <mike.elliott@amdocs.com> | 2019-09-05 19:37:42 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2019-09-05 19:37:42 +0000 |
| commit | a542573fe1330d1ff38bd602a8dfc3e0ca9d8e3b (patch) | |
| tree | 7344de63883f0716e5962ef202283742213a8ece /etc/requirements.txt | |
| parent | f2460622d0ac5a660cf2b85a7e595355e10f961c (diff) | |
Update git submodules
* Update docs/submodules/oom.git from branch 'master'
to 8a45ff1c6b51fdc6cf5dae9c0e84899fdb341a33
- Merge "Move PORTAL Storage access to RWO"
- Move PORTAL Storage access to RWO
Today when deploying Portal 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).
Portal PVC are only used by a mariadb instance or a cassandra instance.
Thus we don't need RWX.
Change-Id: I706e13759d3af829d61d7a33d068263aaf9e9158
Issue-ID: PORTAL-724
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Diffstat (limited to 'etc/requirements.txt')
0 files changed, 0 insertions, 0 deletions