What's needed to deploy ONAP


ONAP is a set of different applications. Since Casablanca release, the preferred way to deploy ONAP is OOM (ONAP Operations Manager).

OOM is a set of helm charts + an helm plugin (deploy).

Each helm chart will deploy on a Kubernetes cluster a component of ONAP (AAI, SO, VFC, ...).

helm deploy plugin will simplify the deployment of the whole solution (faster deployment, use of standard helm metadata storage).


So in order to deploy ONAP, you'll need a working kubernetes (Ingress, Storage class, CNI, ...) environment + helm installed (see software requirements for the correct version to use according to the ONAP version).

On top of this Kubernetes installation, you may also need third party components for specific use cases:

  • Cert Manager if you want to use CMPv2 certificates in DCAE and SDNC
  • Prometheus (preferrably installed with this helm chart) if you want to scrape some metrics
  • Strimzi (PoC in Jakarta, default in Kohn) for Kafka deployment

Strategy to deploy the stack


OOM and Integration team has decided to take a modular approach in order to fulfill all the operations for deploying and validating an ONAP instance:

  • Create the virtual machines

  • Deploy Kubernetes

  • Deploy Platform Services on Kubernetes
  • Deploy ONAP
  • Test ONAP

Important choices have been made:

  • All the deployments are using Gitlab CI
  • All deployments are using ansible playbooks
  • An "orchestrator" of Gitlab CI deployment is used

Chained CI: the Gitlab CI deployment "orchestrator"

Chained CI is a dynamic gitlab ci pipeline manage which will call an underneath pipeline at each stage, wait for completion, retrieve artifacts and move into the next stage if sucessful

Via a declarative (yaml) file, we can:

  • chain any pipeline
  • use outputs of previous stages as input of a stage

Chained CI configuration is mainly splitted in 4 types of files:


More Information :

official documentation: https://docs.onap.org/projects/onap-integration/en/latest/onap-integration-ci.html#integration-ci

Creating virtual machines

input

  • the description of the wanted infrastructure (networks, servers, volume, floating IPs, ...)
  • credentials to use IaaS API

output

  • an inventory file with the created machines and their purpose

Implementations:

OS Infra Manager for OpenStack deployments

AZ Infra Manager for Azure VM deployments

Creating Kubernetes cluster

input

  • an inventory file with server with specific groups:
    • kube-master for servers hosting API part of K8S
    • etcd for servers hosting etcd
    • kube-worker for servers hosting "compute" part of K8S
    • k8s-cluster with kube-node and kube-worker servers
    • k8s-full-cluster with all the servers (master, etcd, worker, jumphost)

output

  • a deployed kubernetes cluster
  • the admin kube config

implementations

Kubespray Automatic installation (used in dailies / weeklies)

RKE Automatic installation (not used anymore)

RKE2 Automatic installation (used internally)

AKS Automatic installation (used for gating)

Adding Services to the Kubernetes cluster

input

  • a valid kube config
  • an accessible kubernetes API

output

  • installed platform components (helm, prometheus, others)

implementations

This installation is done in the "postconfiguration" part of the Kubernetes cluster project.

There are 2 types of implementations :

Deploying ONAP

input

  • a valid kube config
  • helm
  • possibly an override file to choose which components to use / specific configuration for ONAP or some components

output

  • a (working hopefully) ONAP deployment

implementation

ONAP OOM Automatic installation

ONAP OOM Automatic installation refresh (not used today on community deployments unfortunately)

Testing ONAP

input

  • a valid kueb config
  • the name of the namespace where ONAP is installed (onap by default)
  • a docker service

output

  • a report on the performed tests

implementation

Xtesting ONAP

Specificities of ONAP Dailies / Weeklies on Orange premices


Openstack API is not present on Internet and thus all calls must be made via a jumphost (rebond.opnfv.fr)

Specificities of ONAP gating on Azure


As Azure has no OpenStack APIs, a small openstack instance using devstack (using DevStack Automatic Installation) is created near each worker.

Gating

Gating is built on top of "automatic deployment" seen before.

As for daily deployments, two chains in chained ci are created per gating environment (2 gating environment today):

  • Infrastructure deployment (Virtual Machines + Kubernetes + Platform services + Dedicated OpenStack)
  • ONAP deployment and test

One of the difference is that first one will not trigger the second one.

Infrastructure deployment chain is meant to be performed once in a while (after ~100 days, artifacts are too old in gitlab and it must be reinstalled)

ONAP deployment and test chain is meant to be performed anytime a gate is ready to be launched.

As we have a limited number of platform and potentially a bigger number of gates to be performed, a queue system needs to be put in front.

At the time of creation of this gating system, no "out of the box" queue system was found (or understood, we never understood how to use zuul for example)

So the decision was made to create 4 μservices using a MQTT broker named mosquitto as messenging system:

  • Gerrit 2 MQTT : it will create topics / message for every event sent by Gerrit (via SSH)
  • MQTT 2 Gerrit : it will send comments (optionally with score) to a specific Gerrit review when a message is sent in a specific topic
  • Chained CI MQTT Trigger (master mode) : will listen to message on specific topics and queue them when they belongs to a wanted topic. Will resend them when a worker ask for a job
  • Chained CI MQTT Trigger (worker mode) : when free, will listen to message on specific topics and launch a gate (if elected) when receiving one. Will ask for Job every xx seconds when free

Some details are given in the but this is how it's done in the two "main" cases:

Workers are free

  1. A new patchset is created on a watched repo (OOM for example)
  2. Gerrit2MQTT create a message on /onap/oom/patchset-created
  3. Chained CI MQTT Trigger Master reads the message and put it in internal queue
  4. Worker is free and propose to use
  5. Master will acknowledge and remove the message from the queue
  6. Worker will start a chained ci and wait for completion. According to the completion status, it will retrieve failed jobs and abstract messages
  7. Worker will send them to gerrit notification topic
  8. MQTT 2 Gerrit will see the message, retrieve Gerrit number and Patchset number and upload the message

Workers are not free

  1. A new patchset is created on a watched repo (OOM for example)
  2. Gerrit2MQTT create a message on /onap/oom/patchset-created
  3. Chained CI MQTT Trigger Master reads the message and put it in internal queue
  4. Later, a worker is free and send a message to its master to announce it can take a job
  5. Master dequeues the oldest message and resend it
  6. Worker proposes to use
  7. Master acknowledges and removes the message from the queue
  8. Worker starts a chained ci and wait for completion. According to the completion status, it retrieves failed jobs and abstract messages
  9. Worker sends abstract and failed job list gerrit notification topic
  10. MQTT 2 Gerrit will see the message, retrieve Gerrit number and Patchset number and upload the message
  11. Worker announces it's free

Current deployments

All Gating μservices are deployed on Azure ONAP "gating" kubernetes (alongside with a nexus)

Each gating system has a Chained CI MQTT Trigger worker μs.

One Chained CI MQTT Trigger master is created (we can have several that would monitor different repos / have different workers)


Maintenance work on gating


Access to gating systems


You need to have given your ssh key to one of the admins


then, put in your .ssh/config for access to gating systems:


Host rebond.francecentral.cloudapp.azure.com
  User cloud

Host azure*.onap.eu *.integration.onap.eu
  User cloud
  StrictHostKeyChecking no
  CheckHostIP no
  UserKnownHostsFile /dev/null
  ProxyJump rebond.francecentral.cloudapp.azure.com

# Networks used in Azure cloud
Host 192.168.64.* 192.168.65.* 192.168.53.* 192.168.66.* 192.168.67.*
  ProxyJump rebond.francecentral.cloudapp.azure.com
  StrictHostKeyChecking no
  CheckHostIP no
  UserKnownHostsFile /dev/null
  User cloud


Access to weeklies/dailies in Orange can be done by adding this to your .ssh/config (if granted):


Host rebond.opnfv.fr
 User user

Host master*.onap.eu *.daily.onap.eu *.internal.onap.eu *-weekly.onap.eu istanbul.onap.eu
  User debian
  StrictHostKeyChecking no
  CheckHostIP no
  UserKnownHostsFile /dev/null
  ProxyJump rebond.opnfv.fr


Full filesystem

filesystem of jumphost is full and therefore no tests can be launched

check (on jumphost):

df -h

remediation: clean docker

docker system prune -a

Full OpenStack

Clean on OpenStack has not been perfomed and we cannot start new tests on gate

check (on jumphost):

openstack --os-cloud admin stack list

it should be blank or at least with very recent creation time

remediation: clean openstack

openstack --os-cloud admin stack delete UUIDs_OF_STACKS

Lost integration images

ONAP images are not anymore on nexus3.onap.org

check: verify that images are present on nexus3

remediation: create a ticket

Too old system

Gate is quite old and cannot work again

check (on jumphost): uptime on jumphost is more than 100 days and gates are behaving weirdly

uptime

remediation : reinstall gate

Gating reinstallation

To reinstall ONAP Gating instance two pipelines are used. Both are saved as "Scheduled" (but disabled) on Pipeline Schedules · Orange-OpenSource / lfn / ci_cd / chained-ci · GitLab repo. The schedules are:

  • ONAP Gating Azure 3 - to recreate Gating 3,
  • ONAP Gating Azure 4 - to recreate Gating 4.

It's needed only to run these pipelines (if user is allowed) and wait for finish. It's also required to disable gating system before reinstallation. To do it it's needed to login on Gating bastion (rebond.francecentral.cloudapp.azure.com) and scale one of the required deployments running on "onap-gating" kubernetes namespace:

  • chained-ci-mqtt-trigger-worker-7 - Gating 3 deployment,
  • chained-ci-mqtt-trigger-worker-8 - Gating 4 deployment.

To scale it down (disable it) call

$ kubectl -n onap-gating scale deployment/<deployment-you-want-to-scale-down> --replicas=0

After successful recreation of gating lab bring it back to work using

$ kubectl -n onap-gating scale deployment/<deployment-you-want-to-scale-down> --replicas=1

command.

To log in gating system you need to call (being on bastion [rebond.francecentral.cloudapp.azure.com])

Gating 3

$ ssh azure3.onap.eu

Gating 4

$ ssh azure4.onap.eu

Certificate issues

cert-manager is responsible for handling certificates (issued by Let's Encrypt). In case of issues with certificates (like outdated ones) start with cert-manager logs analysis.

Up to now two issues occurred. After transferring ownership of onap.eu, cert-manager was unable to issue new certificates due to DNS challenge failing. This was solved by changing challenge method to DNS. It can be done in Issuer resource that is responsible for requesting new certificates from Let's Encrypt. After changes solver section looks like this:

solvers:
- http01:
    ingress:
      class:  nginx

Another issue that occurred was caused by two ingresses that are responsible for different subdomains using the same TLS secret. In this case solution was very simple - changing name of secret in ingress. After that cert-manager will automatically request for new certificate from Let's Encrypt and save it under new name. In order to make it work Ingress also needs following annotations to be present (in metadata section):

metadata:
  annotations:
    kubernetes.io/ingress.class: "nginx"    
    cert-manager.io/issuer: "{{ name_of_responsible_issuer }}"

Obviously {{ name_of_responsible_issuer }} should be changed to appropriate name if Issuer resource.

  • No labels