ONAP/K8S Deployment OOM Team Sep, 2017

Agenda HW Requirements Describe deployment process Present next development steps

A step-by-step explanation on how to deploy ONAP on Kubernetes: OOM Wiki and Recording A step-by-step explanation on how to deploy ONAP on Kubernetes: https://wiki.onap.org/display/DW/ONAP+on+Kubernetes A video recording of a demo: https://wiki.onap.org/download/attachments/11930015/K 8s_In_Developer_Lab.mp4

Minimum: Rancher: Alternative: HW Requirements k8s master: 2 CPU, 8Gb RAM, 20Gb Disk k8s node: 8 CPU, 64Gb RAM, 100Gb Disk Rancher: Rancher (master): 2 CPU, 8Gb RAM, 20Gb Disk k8s node: 16 CPU, 64Gb RAM, 100Gb Disk Alternative: 3 k8s nodes: 8 CPU, 32Gb RAM, 80Gb Disk

Kubernetes (k8s) For k8s info: http://k8s.io

HL Deployment Process - Preparation

HL Deployment Process - Configuration Deploy config pod to all nodes or to one node and share it via NFS. The pod brings all configuration files, secrets, DBs etc. It creates /dockerdata-nfs directory on each node. This location will later be mapped to containers that will run on this node.

HL Deployment Process - components Deploy all components. Components have each an own namespace. In a namespace there may be multiple pods. There is an order in which pods should start. This order is achieved by readiness container that runs before pod deployment and ensures that relevant dependencies (other pods) are met.

Deployment Process For each component (behind the scenes): Creation of Namespace (onap-XYZ, e.g. onap-appc) Creation of Services (mapping of internal to internal ports) Creation of pods init stage runs readiness which waits for other pods to start Map Environment Variables start containers (dockers) map volumes (files / directories)

Next Steps Configuration Management – build infrastructure to provide simple and efficient parameter values per deployment Replacement of configuration pod with ConfigMaps and Secrets Deployment of DCAE gen2 Images download pre-deployment in order to make first deployment faster

THANK YOU