Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 2 Next »

CDS can be deployed to minikube just like all other ONAP components.

Install Kubernetes, kubectl and Helm clients according to instructions here.

Storage Class

In minikube mariadb-galera has problems to deploy because of persistence problems:

Maridb-galera problem in Minikube 
2019-08-23  6:26:17 140342013503744 [Note] mysqld (mysqld 10.1.24-MariaDB) starting as process 1 ...
2019-08-23  6:26:17 140342013503744 [Note] WSREP: Read nil XID from storage engines, skipping position init
2019-08-23  6:26:17 140342013503744 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib64/galera/libgalera_smm.so'
2019-08-23  6:26:17 140342013503744 [Note] WSREP: wsrep_load(): Galera 25.3.20(r3703) by Codership Oy <info@codership.com> loaded successfully.
2019-08-23  6:26:17 140342013503744 [Note] WSREP: CRC-32C: using hardware acceleration.
2019-08-23  6:26:17 140342013503744 [Note] WSREP: Found saved state: 00000000-0000-0000-0000-000000000000:-1, safe_to_bootsrap: 1
2019-08-23  6:26:17 140342013503744 [ERROR] WSREP: Requested size 134219048 for '/var/lib/mysql//galera.cache' exceeds available storage space 0: 28 (No space left on device)
         at galerautils/src/gu_fdesc.cpp:FileDescriptor():101
2019-08-23  6:26:17 140342013503744 [ERROR] WSREP: wsrep::init() failed: 7, must shutdown
2019-08-23  6:26:17 140342013503744 [ERROR] Aborting

You can check which storageclass you'll need by using "kubectl get sc":

When deploying cds or other ONAP components needing mariadb-galera, override "global.persistence.storageClass" with correct storage class.

Deploy CDS 

helm upgrade --install dev ./onap --namespace onap \
--set cds.enabled=true \
--set cds.cds-blueprints-processor.dmaapEnabled=false \
--set global.persistence.storageClass=standard

Deploy CDS with more overrides e.g. different image versions

helm upgrade --install dev ./onap --namespace onap \
--set cds.enabled=true \
--set cds.cds-blueprints-processor.dmaapEnabled=false \
--set global.persistence.storageClass=standard \
--set cds.cds-blueprints-processor.image=onap/ccsdk-blueprintsprocessor:0.7.0-STAGING-latest \
--set cds.cds-command-executor.image=onap/ccsdk-commandexecutor:0.7.0-STAGING-latest \
--set cds.cds-ui.image=onap/ccsdk-cds-ui-server:0.7.0-STAGING-latest \
--set global.pullPolicy=IfNotPresent

Normally Helm charts (e.g. image versions) should be kept completely in sync with related software version, but for CDS this has not been the case. This also leads to problems that CDS may not work in the Kubernetes (where is should be run). Developers, please test CDS daily in the Kubernetes and update OOM git repo for Helm charts changes.


  • No labels