You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

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:

ComponentMicro serviceNeeds persistenceIs persistentTest resultsComments

aaf





AAF team, please advise - Ramprasad Koya


aaf (authz-service)
No


aaf-cs (cassandra)ProbablyNo

aai



AA&I team, please advise - James Forsyth


aai-deployment (haproxy)NoNo


aai-resources
No


aai-traversal


No


data-router
?
Dynamic data (/opt/app/data-router/dynamic/) is mapped to a host (k8s node) directory

elasticsearchProbably?
Data (/usr/share/elasticsearch/data) is mapped to a host (k8s node) directory

hbaseProbablyNo


modelloader
No


search-data-service
No


sparky-be
No

appc



APPC team, please advise - Randa Maher

appc
No


db (mysql)YesYes
/var/lib/mysql is mapped to a persistent volume
clamp



CLAMP team, please advise - Gervais-Martial Ngueko

clamp

NoNo


mariadbYesYes

cli



CLI team, please advise - user-67d6f

cli
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


elasticsearchYes

Yes




logstashNoNo


kibanaNoNo

message-router



DMaaP team, please advise - Ramprasad Koya

dmaap
No


kafkaYesYes


zookeeperYesYes

msb



MSB team, please advise - HuabingZhao


msb-discovery
No


msb-consul
No


msb-eag
No


msb-iag


No

mso



SO team, please advise - Seshu Kumar Mudiganti

mso
No


mariadbYesYes

multicloud



MultiCloud team, please advise - xinhuili

framework
No


multicloud-ocata
No


multicloud-vio
No


multicloud-windriver
No

policy



Policy team, please advise - Pamela Dragosh

mariadbYesNo


pap
No


pdp
No


drools
No


nexus
No


brmsgw
No

portal



Portal team, please advise - Manoop Talasila

portal-apps




mariadbYesYes


portal-widgets




portal-vncNoNo

robot



OOM team

robotNoNo

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

  • 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)

sdncYesNo
Need to persist /opt/opendaylight/current and ".installed" file

sdnc admin portal
No


mysqlYesYes


dgbuilder
No


dmaap listener
No


ueb listener
No

vfc



Yan Yang - Could you please explain how the components are persisted in OOM (kubernetes)? (For example: vfc-catalog-deployment.yaml)


lcmYesYes


resmanagerYesYes


catalogYesYes



vnflcmYesYes


vnfmgrYesYes


vnfresYesYes


gvnfmadapter




juju-vnfmadapter




hw-vnfmadapter




zte-vmanager




nokia-vfcadapter






zte-sfc-driver




workflow-engine-service




activity-extension




emsdriver





  • No labels