...
The OOM (ONAP Operation Manager) project has pushed Kubernetes based deployment code to the oom repository. This page details getting ONAP running (specifically the vFirewall demo) on Kubernetes for various virtual and native environments.
Undercloud Installation
...
There are several options - currently Rancher is a focus as a thin wrapper on Kubernetes.
...
ONAP deployment in kubernetes is modelled in the oom project as a 1:1 set of service:pod sets (1 pod per docker container). The fastest way to get ONAP Kubernetes up is via Rancher.
Platform Primary platform is Ubuntu 16.04 VMs on VMWare Workstation 12.5 on a up to two 64Gb/6-core 5820K Windows 10 systems (but a bare metal set of Ubuntu servers will work the same)
Currently editing this (adding rancher details) over the morning of 20170706 so bear with me...
.
Secondary platform is 3 NUCs (i7/i5 with 16G each)
Install only the 1.12.x (currently 1.12.6) version of Docker (the only version that works with Kubernetes in Rancher 1.6) Install rancher (use 8880 instead of 8080) In Rancher UI (http://127.0.0.1:8880) , Set IP name of master node in config, create a new onap environment as Kubernetes (will setup kube containers), stop default environment register your host(s) - run following on each host (get from "add host" menu) # sudo docker run --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher rancher/agent:v1.2.2 http://192.168.163.131:8880/v1/scripts/BBD465D9B24E94F5FBFD:1483142400000:IDaNFrug38QsjZcu6rXh8TwqA4 paste kubectl config from rancher # mkdir ~/.kube # vi ~/.kube/config clone oom (scp your onap_rsa private key first) ~/onap# git clone ssh:/ /michaelobrien@gerrit.onap.org:29418/oom fix nexus3 security temporarily for
Wait until all the hosts show green in rancher, then run the script that wrapps all the kubectl commands ~/onap/oom/kubernetes/oneclick# vi createAll.bash /oneclick# ./createAll.bash -n onap Wait until the containers are all up - you should see... |
|---|
Three host Kubernetes cluster in Rancher
In this case 3 Intel NUCs running Ubuntu 16.04.2 natively
Target Deployment State
root@obriensystemsucont0:~/onap/oom/kubernetes/oneclick# kubectl get pods --all-namespaces -o wide
...
NAMESPACE master:20170705 | NAME | READY | STATUS | RESTARTS (in 14h) | Notes |
|---|---|---|---|---|---|
| onap-aai | aai-service-346921785-624ss | 1/1 | Running | 0 | |
| onap-aai | hbase-139474849-7fg0s | 1/1 | Running | 0 | |
| onap-aai | model-loader-service-1795708961-wg19w | 0/1 | Init:1/2 | 82 | |
| onap-appc | appc-2044062043-bx6tc | 1/1 | Running | 0 | |
| onap-appc | appc-dbhost-2039492951-jslts | 1/1 | Running | 0 | |
| onap-appc | appc-dgbuilder-2934720673-mcp7c | 1/1 | Running | 0 | |
| onap-dcae | not yet pushed | Note: currently there are no DCAE containers running yet (we are missing 6 yaml files (1 for the controller and 5 for the collector,staging,3-cdap pods)) - therefore DMaaP, VES collectors and APPC actions as the result of policy actions (closed loop) - will not function yet. | |||
| onap-dcae-cdap | not yet pushed | ||||
| onap-dcae-stg | not yet pushed | ||||
| onap-dcae-coll | not yet pushed | ||||
| onap-message-router | dmaap-3842712241-gtdkp | 0/1 | CrashLoopBackOff | 164 | |
| onap-message-router | global-kafka-89365896-5fnq9 | 1/1 | Running | 0 | |
| onap-message-router | zookeeper-1406540368-jdscq | 1/1 | Running | 0 | |
| onap-mso | mariadb-2638235337-758zr | 0/1 | Running | 0 | |
| onap-mso | mso-3192832250-fq6pn | 1/1 | CrashLoopBackOff | 167 | |
| onap-policy | brmsgw-568914601-d5z71 | 0/1 | Init:0/1 | 82 | |
| onap-policy | drools-1450928085-099m2 | 0/1 | Init:0/1 | 82 | |
| onap-policy | mariadb-2932363958-0l05g | 1/1 | Running | 0 | |
| onap-policy | nexus-871440171-tqq4z | 0/1 | Running | 0 | |
| onap-policy | pap-2218784661-xlj0n | 1/1 | Running | 0 | |
| onap-policy | pdp-1677094700-75wpj | 0/1 | Init:0/1 | 82 | |
| onap-policy | pypdp-3209460526-bwm6b | 0/1 | Init:0/1 | 82 | |
| onap-portal | portalapps-1708810953-trz47 | 0/1 | Init:CrashLoopBackOff | 163 | Initial dockerhub mariadb download issue - fixed |
| onap-portal | portaldb-3652211058-vsg8r | 1/1 | Running | 0 | |
| onap-portal | vnc-portal-948446550-76kj7 | 0/1 | Init:0/5 | 82 | |
| onap-robot | robot-964706867-czr05 | 1/1 | Running | 0 | |
| onap-sdc | sdc-be-2426613560-jv8sk | 0/1 | Init:0/2 | 82 | |
| onap-sdc | sdc-cs-2080334320-95dq8 | 0/1 | CrashLoopBackOff | 163 | |
| onap-sdc | sdc-es-3272676451-skf7z | 1/1 | Running | 0 | |
| onap-sdc | sdc-fe-931927019-nt94t | 0/1 | Init:0/1 | 82 | |
| onap-sdc | sdc-kb-3337231379-8m8wx | 0/1 | Init:0/1 | 82 | |
| onap-sdnc | sdnc-1788655913-vvxlj | 1/1 | Running | 0 | |
| onap-sdnc | sdnc-dbhost-240465348-kv8vf | 1/1 | Running | 0 | |
| onap-sdnc | sdnc-dgbuilder-4164493163-cp6rx | 1/1 | Running | 0 | |
| onap-sdnc | sdnc-portal-2324831407-50811 | 0/1 | Running | 25 | |
| onap-vid | vid-mariadb-4268497828-81hm0 | 0/1 | CrashLoopBackOff | 169 | |
| onap-vid | vid-server-2331936551-6gxsp | 0/1 | Init:0/1 | 82 |
I get the same container issues on 3 different deployments (virtual Ubuntu on 2 separate VMWare based machines, and a 3 node NUC cluster). For example the APPC 3-pod service is running fine.
But the 2-pod VID service has failed startup.
Cloning details
Install the latest version of the OOM (ONAP Operations Manager) project repo - specifically the ONAP on Kubernetes work just uploaded June 2017
...