OOM Deployment on Public Cloud



Storage Class issue



OOM mostly deploy volumes using a shared NFS folder and specific "folder" on top of it. This won't be easy on a public cloud and move to Storage Class is needed.

Also, using "RWO" (read by many nodes and write by one node) should be the standard for access (or Read Only) as "RWX" is not supported by most of the storage classes (see https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes).



Here's the list of PVC asking for RWX:

  • kafka-data-onap-dmaap-message-router-kafka-0

  • kafka-data-onap-dmaap-message-router-kafka-1

  • kafka-data-onap-dmaap-message-router-kafka-2

  • onap-aaf-aaf-config-pvc

  • onap-aaf-aaf-hello-pvc

  • onap-aaf-aaf-status-pvc

  • onap-appc-appc-ansible-server-playbook-onap-appc-appc-ansible-server-0

  • onap-appc-appc-db-data-onap-appc-appc-db-0

  • onap-appc-appc-db-data-onap-appc-appc-db-1

  • onap-appc-appc-db-data-onap-appc-appc-db-2

  • onap-clamp-clamp-dash-es

  • onap-clamp-clampdb

  • onap-contrib-awx-postgres

  • onap-contrib-netbox-postgres

  • onap-contrib-netbox-static

  • onap-dmaap-dmaap-dr-db-data-onap-dmaap-dmaap-dr-db-0

  • onap-dmaap-dmaap-dr-db-data-onap-dmaap-dmaap-dr-db-1

  • onap-dmaap-dmaap-dr-node-event-logs-pvc-onap-dmaap-dmaap-dr-node-0

  • onap-dmaap-dmaap-dr-node-spool-data-pvc-onap-dmaap-dmaap-dr-node-0

  • onap-log-log-elasticsearch

  • onap-mariadb-galera-mariadb-galera-data-onap-mariadb-galera-mariadb-galera-0

  • onap-mariadb-galera-mariadb-galera-data-onap-mariadb-galera-mariadb-galera-1

  • onap-mariadb-galera-mariadb-galera-data-onap-mariadb-galera-mariadb-galera-2

  • onap-modeling-modeling-genericparser

  • onap-modeling-modeling-mariadb-data-onap-modeling-modeling-mariadb-0

  • onap-modeling-modeling-mariadb-data-onap-modeling-modeling-mariadb-1

  • onap-modeling-modeling-mariadb-data-onap-modeling-modeling-mariadb-2

  • onap-multicloud-multicloud-k8s-mongo-data

  • onap-nbi-nbi-mariadb

  • onap-nbi-nbi-mongo-data

  • onap-oof-cmso-db-data-onap-oof-cmso-db-0

  • onap-policy-nexus

  • onap-policy-policydb

  • onap-pomba-pomba-data-router

  • onap-pomba-pomba-elasticsearch

  • onap-portal-portal-cassandra

  • onap-portal-portal-db

  • onap-robot-robot

  • onap-sdc-sdc-es

  • onap-sdnc-cds-blueprints

  • onap-sdnc-cds-db-data-onap-sdnc-cds-db-0

  • onap-sdnc-nengdb-data-onap-sdnc-nengdb-0

  • onap-vfc-vfc-catalog

  • onap-vfc-vfc-mariadb-data-onap-vfc-vfc-mariadb-0

  • onap-vfc-vfc-mariadb-data-onap-vfc-vfc-mariadb-1

  • onap-vfc-vfc-mariadb-data-onap-vfc-vfc-mariadb-2

  • zookeeper-data-onap-dmaap-message-router-zookeeper-0

  • zookeeper-data-onap-dmaap-message-router-zookeeper-1

  • zookeeper-data-onap-dmaap-message-router-zookeeper-2



Status of tickets:



key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh