CPS-175 - Getting issue details... STATUS
Application Ports Reserved for CPS, and xNF
CPS with xNF: 31205
Deployment
Needs to be defined, what Honolulu approach we want. ATM approach is to have 1 with option of enable 2 as well
Deployment can be:
- CPS
- CPS and xNF
- Only xNF?
Database:
At the moment we will reuse ONAP progress Db
Healthy
Further analysis needs to be done in this are. Will be enough with Integrating to OOM, and what OOM provides as life cycle.
Scalability
At the moment we are not ready for scalability. Needs further analysis to progress on this are.
Certificates
We should use / expose the service using https. For this we will need certificates...
Deployment steps
virtualbox + Ubuntu 20.04 + Microk8s 1.15 + Helm 2.16 + docker 19.03.8
snap install microk8s --classic --channel=1.15/stable
microk8s enable storage
microk8s enable dns
snap install helm --classic --channel=2.16/stable
microk8s kubectl -n kube-system create serviceaccount tiller
microk8s kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
helm init --service-account tiller
microk8s kubectl -n kube-system rollout status deploy/tiller-deploy
helm repo remove stable
git clone -b master http://gerrit.onap.org/r/oom --recurse-submodules
cd oom/kubernetes
make repo
make
helm install local/onap -n onap \
--namespace onap \
--set cps.enabled=true \
--set postgres.enabled=true \
--set global.masterPassword=random \
--set global.persistence.storageClass=microk8s-hostpath
helm list