...
OS | VIM | Description | Status | Links | |
---|---|---|---|---|---|
Ubuntu 16 !Redhat !OSX | Bare Metal VMWare | Racher | Recommended approach Issue with kubernetes support only in 1.12 (obsolete docker-machine) on OSX[root@obrien-b2 oneclick]# curl https | http://releasesrancher.com/docs/rancher/v1.com/install-docker/1.12.sh | sh % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 16609 100 16609 0 0 14927 0 0:00:01 0:00:01 --:--:-- 14949 + sh -c 'sleep 3; yum -y -q install docker-engine-1.12.6' Package docker-engine is obsoleted by docker-ce, trying to install docker-ce-17.06.0.ce-1.el7.centos.x86_64 instead Error: Package: docker-ce-17.06.0.ce-1.el7.centos.x86_64 (docker-ce-edge) Requires: container-selinux >= 2.9 | http://rancher.com/docs/rancher/v1.6/en/quick-start-guide/ |
Linux | Bare Metal | Kubernetes Directly on RHEL 7.3 (VMs in this case) | In progress | https://kubernetes.io/docs/getting-started-guides/scratch/ | |
OSX Linux | CoreOS | On Vagrant (Thanks Yves) | Issue: the coreos VM 19G size is insufficient | https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant-single.html Implement OSX fix for Vagrant 1.9.6 https://github.com/mitchellh/vagrant/issues/7747 Avoid the kubectl lock https://github.com/coreos/coreos-kubernetes/issues/886 Nexus auth issues fixed | OSX | MInikube on VMWare Fusion | minikube VM not restartable | https://github.com/kubernetes/minikube | RHEL 7.3 | Redhat Kubernetes | services deploy, but pod IP's not reachable, likely my missing 2 networks (public, onap_oam) retry with kubectl exec | https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/getting_started_with_kubernetes/ |
ONAP Installation
Quickstart Installation
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 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)
...
6/en/quick-start-guide/ | ||||
Linux | Bare Metal | Kubernetes Directly on RHEL 7.3 (VMs in this case) | In progress | https://kubernetes.io/docs/getting-started-guides/scratch/ |
OSX Linux | CoreOS | On Vagrant (Thanks Yves) | Issue: the coreos VM 19G size is insufficient | https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant-single.html Implement OSX fix for Vagrant 1.9.6 https://github.com/mitchellh/vagrant/issues/7747 Avoid the kubectl lock https://github.com/coreos/coreos-kubernetes/issues/886 |
OSX | MInikube on VMWare Fusion | minikube VM not restartable | https://github.com/kubernetes/minikube | |
RHEL 7.3 | Redhat Kubernetes | services deploy, fix kubectl exec | https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/getting_started_with_kubernetes/ |
ONAP Installation
Quickstart Installation
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 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...
register your host(s) # 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 ~/onap# git clone ssh://michaelobrien@gerrit.onap.org:29418/oom fix nexus3 security ~/onap/oom/kubernetes/oneclick# vi createAll.bash |
---|
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 | |
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 |
...
Cloning details
Install the latest version of the OOM (ONAP Operations Manager) project repo - specifically the ONAP on Kubernetes work just uploaded June 2017
...
git clone ssh://yourgerrituserid@gerrit.onap.org:29418/oom cd oom/kubernetes/oneclick Versions oom : master (1.1.0-SNAPSHOT) onap deployments: 1.0.0 |
---|
Rancher kubectl config
Nexus3 security settings
Fix nexus3 security for each namespace
Monitor Container Deployment
Kubernetes specific config
...
http://rancher.com/docs/rancher/v1.5/en/hosts/#supported-docker-versions
curl https://releases.rancher.com/install-docker/1.12.sh | sh |
---|
Verify your Rancher admin console is up on the external port you configured above
...
Having issues registering a combined single VM (controller + host) - use your real IP not localhost
In settings | Host Configuration | set your IP [root@obrien-b2 etcd]# sudo docker run -e CATTLE_AGENT_IP="192.168.163.128" --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.128:8080/v1/scripts/A9487FC88388CC31FB76:1483142400000:IypSDQCtA4SwkRnthKqH53Vxoo |
---|
See your host registered
Bare RHEL 7.3 VM - Multi Node Cluster
...