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 7 Next »

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:

  1.  CPS
  2.  CPS and xNF
  3.  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
  • No labels