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


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




  • No labels