ONAP components consist of one or many containers or micro-services. These micro-services can be stateless or state-full. Stateless micro-services do not store data, can be restarted or recreated. State-full micro-services upon restart or recreation can lose their data.
In OOM kubernetes deployment, micro-services are deployed as containers in entities called pods. Kubernetes provides mechanisms for persisting data of pods it manages.
The mechanism of data persistence can be persistent volumes or other (for example nfs provisioner).
The test is to do a use case like vFW and then restart the docker/k8 container and there should be no loss of data.
Analysis of components that need persistence of their data:
| Component | Micro service | Needs persistence | Is persistent | Test results | Comments |
|---|---|---|---|---|---|
aaf | AAF team, please advise - Ramprasad Koya | ||||
| aaf (authz-service) | No | ||||
| aaf-cs (cassandra) | Probably | No | |||
| aai | AA&I team, please advise - James Forsyth | ||||
| aai-deployment (haproxy) | No | No | |||
| aai-resources | No | ||||
| aai-traversal | No | ||||
| data-router | ? | Dynamic data (/opt/app/data-router/dynamic/) is mapped to a host (k8s node) directory | |||
| elasticsearch | Probably | ? | Data (/usr/share/elasticsearch/data) is mapped to a host (k8s node) directory | ||
| hbase | Probably | No | |||
| modelloader | No | ||||
| search-data-service | No | ||||
| sparky-be | No | ||||
| appc | APPC team, please advise - Randa Maher | ||||
| appc | No | ||||
| db (mysql) | Yes | Yes | /var/lib/mysql is mapped to a persistent volume | ||
| clamp | CLAMP team, please advise - Gervais-Martial Ngueko | ||||
clamp | No | No | |||
| mariadb | Yes | Yes | |||
| cli | CLI team, please advise - user-67d6f | ||||
| cli | No | No | |||
| consul | MSB team, please advise - HuabingZhao | ||||
| consul-client | No | ||||
| consul-server | No | ||||
| dcaegen2 | DCAE team, please advise - Lusheng Ji | ||||
| nginx | No | ||||
| heat-bootstrap | No | ||||
| esr | AA&I team, please advise - James Forsyth | ||||
| esrserver | No | ||||
| esrgui | No | ||||
| kube2msb | KUBE 2 MSB team, please advise - HuabingZhao | ||||
| kube2msb | No | ||||
| log | LOG team, please advise - Michael O'Brien | ||||
| elasticsearch | Yes | Yes | |||
| logstash | No | No | |||
| kibana | No | No | |||
| message-router | DMaaP team, please advise - Ramprasad Koya | ||||
| dmaap | No | ||||
| kafka | Yes | Yes | |||
| zookeeper | Yes | Yes | |||
| msb | MSB team, please advise - HuabingZhao | ||||
| msb-discovery | No | ||||
| msb-consul | Yes | No | |||
| msb-eag | No | ||||
msb-iag | No | ||||
| mso | SO team, please advise - Seshu Kumar Mudiganti | ||||
| mso | No | ||||
| mariadb | Yes | Yes | |||
| multicloud | MultiCloud team, please advise - xinhuili | ||||
| framework | No | ||||
| multicloud-ocata | No | ||||
| multicloud-vio | No | ||||
| multicloud-windriver | No | ||||
| policy | Policy team, please advise - Pamela Dragosh | ||||
| mariadb | Yes | No | |||
| pap | No | ||||
| pdp | No | ||||
| drools | No | ||||
| nexus | No | ||||
| brmsgw | No | ||||
| portal | Portal team, please advise - Manoop Talasila | ||||
| portal-apps | |||||
| mariadb | Yes | Yes | |||
| portal-widgets | |||||
| portal-vnc | No | No | |||
| robot | OOM team | ||||
| robot | No | No | |||
| sdc | SDC team, please advise - Michael Lando | ||||
| elasticsearch | Yes | external mounted volume /data/ES/ | |||
| cassandra | Yes | external mounted volume /data/CS/ | |||
| kibana | No | ||||
| front-end | No | ||||
| back-end | No | ||||
| sdnc | SDNC team, please advise - Dan Timoney, Brian Freeman
| ||||
| sdnc | Yes | No | Need to persist /opt/opendaylight/current and ".installed" file | ||
| sdnc admin portal | No | ||||
| mysql | Yes | Yes | |||
| dgbuilder | No | ||||
| dmaap listener | No | ||||
| ueb listener | No | ||||
| uui | Usecase-UI team, please advise - Tao Shen | ||||
| uui | No | ||||
| uui-server | No | ||||
| vfc | VFC team, please advise - Yan Yang Yan Yang - Could you please explain how the components are persisted in OOM (kubernetes)? (For example: vfc-catalog-deployment.yaml) by fujinhua: vfc-catalog has mysql database and redis cache in its own container, if we want to change it to stateless micro service, mysql and redis need be moved to OOM. | ||||
| catalog | No | ||||
| emsdriver | No | ||||
| gvnfmadapter | No | ||||
| hw-vnfmadapter | No | ||||
| juju-vnfmadapter | No | ||||
| nokia-vfcadapter | No | ||||
| nslcm | No | ||||
| resmanager | No | ||||
| vnflcm | No | ||||
| vnfmgr | No | ||||
| vnfres | No | ||||
| workflow | No | ||||
| workflow-engine-service | No | ||||
| ztesdncdriver | No | ||||
| zte-vmanager | No | ||||
| vid | VID team, please advise - Ofir Sonsino | ||||
| vid server | No | No | |||
| mariadb | Yes | Yes | |||
| vnfsdk | VNF SDK team, please advise - Chris Donley | ||||
| refrepo | No | ||||
| postgres | No |
2 Comments
Brian Freeman
Please add a column for "Test results".
The test is to do a use case like vFW and then restart the docker/k8 container and there should be no loss of data.
In OOM today for SDNC - if you do a vFW use case and then stop the k8 container all data in MD-SAL is lost. The same does not happen in the HEAT/Docker version so the persistence for the /opt/opendaylight/current directory is not right in the SDNC OOM config. There is also a ".installed" file after installation that isn't preserved on a restart so SDNC features and DGs are re-installed on a restart (required because the disk subsystem isn't maintained)
Borislav Glozman
Thanks Brian Freeman, Added the column and the comments.
Could /opt/opendaylight/current directory be reduced to only the things that are necessary to persist instead of all odl?