Request access to VM
- Login to https://selfservice-dev.est.tech/login to create a 'booking' for OpenVPN
- Read through the instructions and tips to get familiar with the process (also make sure, that you generate an RSA keypair, seem like that's the only one they accept)
- Request Andrew Fenner and/or Robert Tomczyk for a new account on 'our' VM' (172.16.3.229
)
After you are able to log in you can check the kube config file on the VM. Its recommended to merge that file with your computer's local kube config file. This way you will be able to work from your computer, so you only have to connect to the VPN.
You can use this command to connect from the same directory where your .ovpn is located:
sudo openvpn --config YOUR_USERNAME.xerces.onap.ovpn --auth-nocache
Uninstall CPS
To unistall CPS from a given namespace use this command:
helm uninstall $ONAP_INSTALL_RELEASE_NAME --namespace $ONAP_INSTALL_NAMESPACE
Optionally we can delete the namespace as well
kubectl delete $NAMESPACE
Install (minimal) CPS
First of all we should create a namespace within Kubernetes:
kubectl create namespace $NAMESPACE
Add Xerces Helm repository:
helm repo add xerces http://172.16.3.229/local
(note: the IP address might change. This value worked for us, but if it's not reachable contact Andrew Fenner)
Install the chart with the following command:
helm install $ONAP_INSTALL_RELEASE_NAME xerces/onap -i -f values.yaml -f $ONAP_INSTALL_VALUES_YAML --namespace $ONAP_INSTALL_NAMESPACE --set global.masterPassword=$ONAP_INSTALL_MASTER_PASSWORD --debug
The value of $ONAP_INSTALL_VALUES_YAML must be a relative path from the oom/kubernetes/onap/Chart.yaml to the configuration YAML file that we place under the overrides folder (eg ./resources/overrides/cps-minimal.yaml ).
When the installation is complete we must provide an Ingress srevice to expose CPS to the wider world.
kubectl expose service cps-core --port 9001 --target-port=8080 --name=cps-http-api -n cps --type=NodePort
Update CPS
Upgrade the installment:
helm upgrade $ONAP_INSTALL_RELEASE_NAME xerces/onap -i -f values.yaml -f $ONAP_INSTALL_VALUES_YAML --namespace $ONAP_INSTALL_NAMESPACE --set global.masterPassword=$ONAP_INSTALL_MASTER_PASSWORD --debug
Override YAML
This basic .yaml information should be enough to deploy a CPS instance. Check the comments for explanations.
# we can set pull policy for every image under the global key
global:
pullPolicy: IfNotPresent
cps:
# enable certain services under their respective keys (here we enable CPS etc.)
enabled: true
cps-temporal:
enabled: false
cps-core:
config:
# under the additional section we can affect certain configurations of the Spring Boot application (new prefix for the REST endpoints)
additional:
rest:
api:
cps-base-path: /kiscica
postgres:
config:
pgUserExternalSecret: '{{ .Release.Name }}-postgres-{{ include "common.postgres.secret.userCredentialsUID" . }}'
postgres-init:
config:
# add external secrets to the deployments
pgUserExternalSecret: '{{ .Release.Name }}-postgres-{{ include "common.postgres.secret.userCredentialsUID" . }}'
sdnc:
enabled: false
strimzi:
enabled: true
# set the running number of replicas
replicaCount: 1
Compile onap chart
When you modify the deployment yaml you need to recompile the onap chart (it is not necessary for installation or when you just modify the values.yaml)
compile onap
navigate to the <git>/oom/kubernetes folder
helm package ./onap --dependency-update
upload onap
helm cm-push onap-<version>.tgz xerces -f
missing dependencies
When you run this compilation first you must compile every dependencies too.
First you need to start a local chartmuseum
docker run -p 8879:8080 bitnami/chartmuseum:latest
add local repository to helm
helm repo add local http://localhost:8879/
after it you can compile the whole onap project, it has a make file so it is quiet easy, but take a long time ca. an hour
make build
then you can continue with the second step
Pnf-simulator
Open pnf-simulator's directory in your terminal. Compile and upload must be run once for each cluster.
compile pnf-simulator
helm package ./pnfsim --dependency-update
upload pnf-simulator
helm cm-push pnfsim-0.1.0.tgz xerces -f
install pnf-simulator
helm install pnfsim xerces/pnfsim -f ./pnfsim/values.yaml --namespace <your-namespace> --set global.masterPassword=mySec --debug
uninstall pnf-simulator
helm uninstall pnfsim --namespace <your-namespace>
Troubleshooting
helm repository unreachable on xerces
restart charmuseum on xerces as root:
chartmuseum --storage local --storage-local-rootdir /root/helm3-storage -port 8879 &
EOF Exception
sometimes when you start an install you can see an error message
install.go:192: [debug] Original chart version: "" Error: INSTALLATION FAILED: unexpected EOF helm.go:84: [debug] unexpected EOF INSTALLATION FAILED main.newInstallCmd.func2 helm.sh/helm/v3/cmd/helm/install.go:141 github.com/spf13/cobra.(*Command).execute github.com/spf13/cobra@v1.5.0/command.go:872 github.com/spf13/cobra.(*Command).ExecuteC github.com/spf13/cobra@v1.5.0/command.go:990 github.com/spf13/cobra.(*Command).Execute github.com/spf13/cobra@v1.5.0/command.go:918 main.main helm.sh/helm/v3/cmd/helm/helm.go:83 runtime.main runtime/proc.go:250 runtime.goexit runtime/asm_386.s:1326
It is a bug in helm, not necessary to do anything, just rerun the installation
Strimzi-kafka can not start
You can run only one strimzi-kafka per cluster. When your strimzi-kafka can not start, maybe there is another one on the cluster in a different namespace. Uninstall the other and then restart your strimzi-kafka