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).
Analysis of components that need persistence of their data:
| Component | Micro service | Needs persistence | Is persistent | Comments |
|---|---|---|---|---|
aaf | AAF team, please advise | |||
| aaf (authz-service) | No | |||
| aaf-cs (cassandra) | Probably | No | ||
| aai | AA&I team, please advise | |||
| 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 | |||
| appc | No | |||
| db (mysql) | Yes | Yes | /var/lib/mysql is mapped to a persistent volume | |