Warning: Draft Content
This wiki is under construction - this means that content here may be not fully specified or missing.
TODO: determine/fix containers not ready, get DCAE yamls working, fix health tracking issues for healing
The OOM (ONAP Operation Manager) project has pushed Kubernetes based deployment code to the oom repository - based on ONAP 1.0 (not 1.1 yet). This page details getting ONAP running (specifically the vFirewall demo) on Kubernetes for various virtual and native environments. This page assumes you have access to any type of bare metal or VM running a clean Ubuntu 16.04 image - either on Rackspace, Openstack, your laptop or AWS spot EC2.
Architectural details of the OOM project is described here - OOM User Guide
Undercloud Installation
Requirements
| Metric | Min | Notes |
|---|---|---|
| RAM | 37G w/o DCAE 50G with DCAE | Note: you need at least 37g RAM (34 for ONAP services - this is without DCAE yet and without running the vFirewall yet). |
| HD | 100G w/o DCAE |
We need a kubernetes installation either a base installation or with a thin API wrapper like Rancher.
There are several options - currently Rancher with Helm on Ubuntu 16.04 is a focus as a thin wrapper on Kubernetes - there are other alternative platforms in the subpage - ONAP on Kubernetes (Alternatives)
| OS | VIM | Description | Status | Nodes | Links |
|---|---|---|---|---|---|
Ubuntu 16.04.2
| Bare Metal VMWare | Rancher | Recommended approach Issue with kubernetes support only in 1.12 (obsolete docker-machine) on OSX | 1-4 | http://rancher.com/docs/rancher/v1.6/en/quick-start-guide/ |
ONAP Installation
Quickstart Installation
1) install rancher, clone oom, run config-init pod, run one or all onap components
***************** Note: uninstall docker if already installed - as Kubernetes only support 1.12.x - as of 20170809 % sudo apt-get remove docker-engine ***************** |
|---|
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 on any bare metal or VM that supports a clean Ubuntu 16.04 install and more than 50G ram.
(on each host) add to your /etc/hosts to point your ip to your hostname (add your hostname to the end). Add entries for all other hosts in your cluster. sudo vi /etc/hosts <your-ip> <your-hostname> Try to use root - if you use ubuntu then you will need to enable docker separately for the ubuntu user sudo su - apt-get update (to fix possible modprobe: FATAL: Module aufs not found in directory /lib/modules/4.4.0-59-generic) (on each host (server and client(s) which may be the same machine)) Install only the 1.12.x (currently 1.12.6) version of Docker (the only version that works with Kubernetes in Rancher 1.6) curl https://releases.rancher.com/install-docker/1.12.sh | sh (on the master only) Install rancher (use 8880 instead of 8080) - note there may be issues with the dns pod in Rancher after a reboot or when running clustered hosts - a clean system will be OK - OOM-236 - Getting issue details... STATUS docker run -d --restart=unless-stopped -p 8880:8080 rancher/server In Rancher UI - dont use (http://127.0.0.1:8880) - use the real IP address - so the client configs are populated correctly with callbacks You must deactivate the default CATTLE environment - by adding a KUBERNETES environment - and Deactivating the older default CATTLE one - your added hosts will attach to the default
Register your host(s) - run following on each host (including the master if you are collocating the master/host on a single machine/vm) For each host, In Rancher > Infrastructure > Hosts. Select "Add Host" Enter IP of host:
Copy command to register host with Rancher,
Execute command on host, for example: % 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 wait for kubernetes menu to populate with CLI install kubectl on the server and optionally the other hosts % curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl % chmod +x ./kubectl % mv ./kubectl /usr/local/bin/kubectl % mkdir ~/.kube % vi ~/.kube/config paste kubectl config from rancher (you will see the CLI menu in Rancher | Kubernetes after the k8s pods are up on your host Click on "Generate Config" to get your content to add into .kube/config Verify that Kubernetes config is good root@obrien-kube11-1:~# kubectl cluster-info Kubernetes master is running at .... Heapster is running at.... KubeDNS is running at .... kubernetes-dashboard is running at ... monitoring-grafana is running at .... monitoring-influxdb is running at ... tiller-deploy is running at.... Install Helm (use 2.3.0 not current 2.6.0) wget http://storage.googleapis.com/kubernetes-helm/helm-v2.3.0-linux-amd64.tar.gz tar -zxvf helm-v2.3.0-linux-amd64.tar.gz mv linux-amd64/helm /usr/local/bin/helm # test helm helm help Undercloud done - move to ONAP clone oom (scp your onap_rsa private key first - or clone anon - Ideally you get a full gerrit account and join the community) see ssh/http/http access links below https://gerrit.onap.org/r/#/admin/projects/oom anonymous http 1.0 branch git clone -b release-1.0.0 http://gerrit.onap.org/r/oom or 1.1/R1 master branch git clone http://gerrit.onap.org/r/oom or using your key git clone -b release-1.0.0 ssh://michaelobrien@gerrit.onap.org:29418/oom or use https (substitute your user/pass) git clone -b release-1.0.0 https://michaelnnnn:uHaBPMvR47nnnnnnnnRR3Keer6vatjKpf5A@gerrit.onap.org/r/oom Wait until all the hosts show green in rancher, then run the createConfig/createAll scripts that wraps all the kubectl commands
OOM-115
-
Getting issue details...
STATUS
Run the setenv.bash script in /oom/kubernetes/oneclick/ (new since 20170817) source setenv.bash (only if you are planning on closed-loop) - Before running createConfig.sh (see below) - make sure your config for openstack is setup correctly - so you can deploy the vFirewall VMs for example vi oom/kubernetes/config/docker/init/src/config/mso/mso/mso-docker.json replace for example "identity_services": [{ run the one time config pod - which mounts the volume /dockerdata/ contained in the pod config-init. This mount is required for all other ONAP pods to function. Note: the pod will stop after NFS creation - this is normal. % cd oom/kubernetes/config % chmod 777 createConfig.sh (1.0 branch only) % ./createConfig.sh -n onap **** Creating configuration for ONAP instance: onap Wait for the config-init pod is gone before trying to bring up a component or all of ONAP - around 15-20 sec - see https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-Waitingforconfig-initcontainertofinish-20sec Note: use only the hardcoded "onap" namespace prefix - as URLs in the config pod are set as follows "workflowSdncadapterCallback": "http://mso.onap-mso:8080/mso/SDNCAdapterCallbackService" Don't run all the pods unless you have at least 40G (without DCAE) or 50G allocated - if you have a laptop/VM with 16G - then you can only run enough pods to fit in around 11G Ignore errors introduced around 20170816 - these are non-blocking and will allow the create to proceed - OOM-146 - Getting issue details... STATUS % cd ../oneclick % vi createAll.bash % ./createAll.bash -n onap -a robot|appc|aai (to bring up a single service at a time) Only if you have >50G run the following (all namespaces) % ./createAll.bash -n onap ONAP is OK if everything is 1/1 in a the following % kubectl get pods --all-namespaces Run the ONAP portal via instructions at RunningONAPusingthevnc-portal 1.1 is currently having helm issues as of 20170825 OOM-219 - Getting issue details... STATUS Wait until the containers are all up Run Initial healthcheck directly on the host cd /dockerdata-nfs/onap/robot ./ete-docker.sh health |
List of Containers
Total pods is 47
Docker container list - source of truth: https://git.onap.org/integration/tree/packaging/docker/docker-images.csv
below any coloured container had issues getting to running state (currently 32 of 33 come up after 45 min) - there are an addition 11 dcae pods - bringing the total to 44 with an additional 4 for appc/sdnc and the config-init pod
NAMESPACE master:20170715 | NAME | READY | Image | STATUS | Notes |
|---|---|---|---|---|---|
| default | config-init | 0/0 | Terminated (Succeeded) | The mount "config-init-root" is in the following location (user configurable VF parameter file below) /dockerdata-nfs/onapdemo/mso/mso/mso-docker.json | |
| onap-aai | aai-service-346921785-624ss | 1/1 | Running | ||
| onap-aai | hbase-139474849-7fg0s | 1/1 | Running | ||
| onap-aai | model-loader-service-1795708961-wg19w | 0/1 | Init:1/2 | ||
| onap-appc | appc-2044062043-bx6tc | 1/1 | Running | ||
| onap-appc | appc-dbhost-2039492951-jslts | 1/1 | Running | ||
| onap-appc | appc-dgbuilder-2934720673-mcp7c | 1/1 | Running | ||
| onap-appc | sdntldb01 (internal) | ||||
| onap-appc | sdnctldb02 (internal) | ||||
| onap-dcae | dcae-zookeeper | 1/1 | wurstmeister/zookeeper:latest | Running | |
| onap-dcae | dcae-kafka | dockerfiles_kafka:latest | debugging | 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. In review: https://gerrit.onap.org/r/#/c/7287/ OOM-5 - Getting issue details... STATUS OOM-62 - Getting issue details... STATUS | |
| onap-dcae | dcae-dmaap | attos/dmaap:latest | debugging | ||
| onap-dcae | pgaas | 1/1 | obrienlabs/pgaas | https://hub.docker.com/r/oomk8s/pgaas/tags/ | |
| onap-dcae | dcae-collector-common-event | 1/1 | Running | persistent volume: dcae-collector-pvs | |
| onap-dcae | dcae-collector-dmaapbc | 1/1 | Running | ||
| |||||
| onap-dcae | dcae-ves-collector | debugging | |||
| onap-dcae | cdap-0 | debugging | |||
| onap-dcae | cdap-1 | debugging | |||
| onap-dcae | cdap-2 | debugging | |||
| onap-message-router | dmaap-3842712241-gtdkp | 0/1 | CrashLoopBackOff | ||
| onap-message-router | global-kafka-89365896-5fnq9 | 1/1 | Running | ||
| onap-message-router | zookeeper-1406540368-jdscq | 1/1 | Running | ||
| onap-mso | mariadb-2638235337-758zr | 1/1 | Running | ||
| onap-mso | mso-3192832250-fq6pn | 0/1 | CrashLoopBackOff | ||
| onap-policy | brmsgw-568914601-d5z71 | 0/1 | Init:0/1 | ||
| onap-policy | drools-1450928085-099m2 | 0/1 | Init:0/1 | ||
| onap-policy | mariadb-2932363958-0l05g | 1/1 | Running | ||
| onap-policy | nexus-871440171-tqq4z | 0/1 | Running | ||
| onap-policy | pap-2218784661-xlj0n | 1/1 | Running | ||
| onap-policy | pdp-1677094700-75wpj | 0/1 | Init:0/1 | ||
| onap-policy | pypdp-3209460526-bwm6b | 0/1 | Init:0/1 | 1.0.0 only | |
| onap-portal | portalapps-1708810953-trz47 | 0/1 | Init:CrashLoopBackOff | Initial dockerhub mariadb download issue - fixed | |
| onap-portal | portaldb-3652211058-vsg8r | 1/1 | Running | ||
| onap-portal | vnc-portal-948446550-76kj7 | 0/1 | Init:0/5 | ||
| onap-robot | robot-964706867-czr05 | 1/1 | Running | ||
| onap-sdc | sdc-be-2426613560-jv8sk | 0/1 | Init:0/2 | ||
| onap-sdc | sdc-cs-2080334320-95dq8 | 0/1 | CrashLoopBackOff | ||
| onap-sdc | sdc-es-3272676451-skf7z | 1/1 | Running | ||
| onap-sdc | sdc-fe-931927019-nt94t | 0/1 | Init:0/1 | ||
| onap-sdc | sdc-kb-3337231379-8m8wx | 0/1 | Init:0/1 | ||
| onap-sdnc | sdnc-1788655913-vvxlj | 1/1 | Running | ||
| onap-sdnc | sdnc-dbhost-240465348-kv8vf | 1/1 | Running | ||
| onap-sdnc | sdnc-dgbuilder-4164493163-cp6rx | 1/1 | Running | ||
| onap-sdnc | sdnctlbd01 (internal) | ||||
| onap-sdnc | sdnctlb02 (internal) | ||||
| onap-sdnc | sdnc-portal-2324831407-50811 | 0/1 | Running | root@obriensystemskub0:~/oom/kubernetes/oneclick# kubectl --namespace onap-sdnc logs -f sdnc-portal-3375812606-01s1d | grep ERR npm ERR! fetch failed https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.1.tgz | |
| onap-vid | vid-mariadb-4268497828-81hm0 | 0/1 | CrashLoopBackOff | ||
| onap-vid | vid-server-2331936551-6gxsp | 0/1 | Init:0/1 |
List of Docker Images
root@obriensystemskub0:~/oom/kubernetes/dcae# docker images missing: # can be replaced by public dockerHub link |
|---|
Verifying Container Startup
to check that config-init has mounted properly do a "ls /dockerdata-nfs"
Cloning details
Install the latest version of the OOM (ONAP Operations Manager) project repo - specifically the ONAP on Kubernetes work just uploaded June 2017
https://gerrit.onap.org/r/gitweb?p=oom.git
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 environment for Kubernetes
setup a separate onap kubernetes environment and disable the exising default environment.
Adding hosts to the Kubernetes environment will kick in k8s containers
Rancher kubectl config
To be able to run the kubectl scripts - install kubectl
Nexus3 security settings
Fix nexus3 security for each namespace
in createAll.bash add the following two lines just before namespace creation - to create a secret and attach it to the namespace (thanks to Jason Hunt of IBM last friday to helping us attach it - when we were all getting our pods to come up). A better fix for the future will be to pass these in as parameters from a prod/stage/dev ecosystem config.
create_namespace() {
kubectl create namespace $1-$2
+ kubectl --namespace $1-$2 create secret docker-registry regsecret --docker-server=nexus3.onap.org:10001 --docker-username=docker --docker-password=docker --docker-email=email@email.com
+ kubectl --namespace $1-$2 patch serviceaccount default -p '{"imagePullSecrets": [{"name": "regsecret"}]}'
} |
|---|
Fix MSO mso-docker.json
Before running pod-config-init.yaml - make sure your config for openstack is setup correctly - so you can deploy the vFirewall VMs for example
vi oom/kubernetes/config/docker/init/src/config/mso/mso/mso-docker.json
| Original | Replacement for Rackspace |
"mso-po-adapter-config": { | "mso-po-adapter-config": { |
|---|
delete/recreate the config poroot@obriensystemskub0:~/oom/kubernetes/config# kubectl --namespace default delete -f pod-config-init.yaml
pod "config-init" deleted
root@obriensystemskub0:~/oom/kubernetes/config# kubectl create -f pod-config-init.yaml
pod "config-init" created
or copy over your changes directly to the mount
root@obriensystemskub0:~/oom/kubernetes/config# cp docker/init/src/config/mso/mso/mso-docker.json /dockerdata-nfs/onapdemo/mso/mso/mso-docker.json
Use only "onap" namespace
Note: use only the hardcoded "onap" namespace prefix - as URLs in the config pod are set as follows "workflowSdncadapterCallback": "http://mso.onap-mso:8080/mso/SDNCAdapterCallbackService",
Monitor Container Deployment
first verify your kubernetes system is up
Then wait 29-45 min for all pods to attain 1/1 state
Kubernetes specific config
https://kubernetes.io/docs/user-guide/kubectl-cheatsheet/
Nexus Docker repo Credentials
Checking out use of a kubectl secret in the yaml files via - https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
Running a Kubernetes Cluster
Details on getting a cluster of hosts running OOM instead of a single large colocated master/host.
Deleting All Containers
Delete all the containers (and services)
./deleteAll.bash -n onap
Delete/Rerun config-init container for /dockerdata-nfs refresh
Delete the config-init container and its generated /dockerdata-nfs share
There may be cases where new configuration content needs to be deployed after a pull of a new version of ONAP.
for example after pull brings in files like the following (20170902)
root@ip-172-31-93-160:~/oom/kubernetes/oneclick# git pull Resolving deltas: 100% (135/135), completed with 24 local objects. From http://gerrit.onap.org/r/oom bf928c5..da59ee4 master -> origin/master Updating bf928c5..da59ee4 kubernetes/config/docker/init/src/config/aai/aai-config/cookbooks/aai-resources/aai-resources-auth/metadata.rb | 7 + kubernetes/config/docker/init/src/config/aai/aai-config/cookbooks/aai-resources/aai-resources-auth/recipes/aai-resources-aai-keystore.rb | 8 + kubernetes/config/docker/init/src/config/aai/aai-config/cookbooks/{ajsc-aai-config => aai-resources/aai-resources-config}/CHANGELOG.md | 2 +- kubernetes/config/docker/init/src/config/aai/aai-config/cookbooks/{ajsc-aai-config => aai-resources/aai-resources-config}/README.md | 4 +- |
see OOM-257 - Getting issue details... STATUS
# check for the pod kubectl get pods --all-namespaces -a # delete the config pod cd ../config kubectl --namespace onap delete -f pod-config-init.yaml --all # delete the fs rm -rf /dockerdata-nfs/onap # rerun the config ./createConfig.bash -n onap
Waiting for config-init container to finish - 20sec
root@ip-172-31-93-160:~/oom/kubernetes/config# kubectl get pods --all-namespaces -a NAMESPACE NAME READY STATUS RESTARTS AGE onap config-init 0/1 ContainerCreating 0 6s root@ip-172-31-93-160:~/oom/kubernetes/config# kubectl get pods --all-namespaces -a NAMESPACE NAME READY STATUS RESTARTS AGE onap config-init 1/1 Running 0 9s root@ip-172-31-93-160:~/oom/kubernetes/config# kubectl get pods --all-namespaces -a NAMESPACE NAME READY STATUS RESTARTS AGE onap config-init 0/1 Completed 0 14s |
Container Endpoint access
Check the services view in the Kuberntes API under robot
robot.onap-robot:88 TCP
robot.onap-robot:30209 TCP
root@obriensystemskub0:~/oom/kubernetes/oneclick# kubectl get services --all-namespaces -o wide onap-vid vid-mariadb None <none> 3306/TCP 1h app=vid-mariadb onap-vid vid-server 10.43.14.244 <nodes> 8080:30200/TCP 1h app=vid-server |
|---|
Container Logs
root@obriensystemskub0:~/oom/kubernetes/oneclick# kubectl --namespace onap-vid logs -f vid-server-248645937-8tt6p 16-Jul-2017 02:46:48.707 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 22520 ms root@obriensystemskub0:~/oom/kubernetes/oneclick# kubectl get pods --all-namespaces -o wide NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE onap-robot robot-44708506-dgv8j 1/1 Running 0 36m 10.42.240.80 obriensystemskub0 root@obriensystemskub0:~/oom/kubernetes/oneclick# kubectl --namespace onap-robot logs -f robot-44708506-dgv8j 2017-07-16 01:55:54: (log.c.164) server started |
|---|
SSH into ONAP containers
Normally I would via https://kubernetes.io/docs/tasks/debug-application-cluster/get-shell-running-container/
Get the pod name via kubectl get pods --all-namespaces -o wide bash into the pod via kubectl -n onap-mso exec -it mso-1648770403-8hwcf /bin/bash |
|---|
Push Files to Pods
Trying to get an authorization file into the robot pod
root@obriensystemskub0:~/oom/kubernetes/oneclick# kubectl cp authorization onap-robot/robot-44708506-nhm0n:/home/ubuntu above works? |
|---|
Running ONAP Portal UI Operations
Running ONAP using the vnc-portal
see Installing and Running the ONAP Demos
or run the vnc-portal container to access ONAP using the traditional port mappings. See the following recorded video by Mike Elliot of the OOM team for a audio-visual reference
Check for the vnc-portal port via (it is always 30211)
obrienbiometrics:onap michaelobrien$ ssh ubuntu@dev.onap.info ubuntu@ip-172-31-93-122:~$ sudo su - root@ip-172-31-93-122:~# kubectl get services --all-namespaces -o wide NAMESPACE NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR onap-portal vnc-portal 10.43.78.204 <nodes> 6080:30211/TCP,5900:30212/TCP 4d app=vnc-portal
launch the vnc-portal in a browser
password is "password"
Open firefox inside the VNC vm - launch portal normally
http://portal.api.simpledemo.openecomp.org:8989/ECOMPPORTAL/login.htm
login and run SDC
Continue with the normal ONAP demo flow at Tutorial: Onboarding and Distributing a Vendor Software Product (VSP)
Running ONAP directly
Get the mapped external port by checking the service in kubernetes - here 30200 for VID on a particular node in our cluster.
fix /etc/hosts as usual
192.168.163.132 portal.api.simpledemo.openecomp.org 192.168.163.132 sdc.api.simpledemo.openecomp.org 192.168.163.132 policy.api.simpledemo.openecomp.org 192.168.163.132 vid.api.simpledemo.openecomp.org |
|---|
In order to map internal 8989 ports to external ones like 30215 - we will need to reconfigure the onap config links as below.
Kubernetes Installation Options
Rancher on Ubuntu 16.04
Install Rancher
http://rancher.com/docs/rancher/v1.6/en/quick-start-guide/
http://rancher.com/docs/rancher/v1.6/en/installing-rancher/installing-server/#single-container
Install a docker version that Rancher and Kubernetes support which is currently 1.12.6
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
Wait for the docker container to finish DB startup
http://rancher.com/docs/rancher/v1.6/en/hosts/
Registering Hosts in Rancher
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
Troubleshooting
Rancher fails to restart on server reboot
Having issues after a reboot of a colocated server/agent
Installing Clean Ubuntu
apt-get install ssh apt-get install ubuntu-desktop |
|---|
Docker Nexus Config
OOM-3 - Getting issue details... STATUS
Out of the box we cant pull images - currently working on a config step around https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
| kubectl create secret docker-registry regsecret --docker-server=nexus3.onap.org:10001 --docker-username=docker --docker-password=docker --docker-email=someone@amdocs.com |
|---|
imagePullSecrets: - name: regsecret |
|---|
Failed to pull image "nexus3.onap.org:10001/openecomp/testsuite:1.0-STAGING-latest": image pull failed for nexus3.onap.org:10001/openecomp/testsuite:1.0-STAGING-latest, this may be because there are no credentials on this request. details: (unauthorized: authentication required)
kubelet 172.17.4.99
OOM Repo changes
20170629: fix on 20170626 on a hardcoded proxy - (for those who run outside the firewall) - https://gerrit.onap.org/r/gitweb?p=oom.git;a=commitdiff;h=131c2a42541fb807f395fe1f39a8482a53f92c60
DNS resolution
ignore - not relevant
Search Line limits were exceeded, some dns names have been omitted, the applied search line is: default.svc.cluster.local svc.cluster.local cluster.local kubelet.kubernetes.rancher.internal kubernetes.rancher.internal rancher.internal
https://github.com/rancher/rancher/issues/9303
OOM-1 - Getting issue details... STATUS
Design Issues
DI 10: 20170724: DCAE Integration
OOM-5 - Getting issue details... STATUS
todo:
docker images need to be pushed to nexus
from: registry.stratlab.local:30002/onap/dcae/cdap:1.0.7
to: nexus3.onap.org:10001/openecomp
OOM-62 - Getting issue details... STATUS
2 persistent volumes also created (controller-pvs, collector-pvs) root@obriensystemskub0:~/oom/kubernetes/oneclick# kubectl get pods --all-namespaces -o wide | grep dcae onap-dcae cdap0-801098998-1j83b 0/1 Init:ImagePullBackOff 0 7m 10.42.170.56 obriensystemskub0 onap-dcae cdap1-1109312935-sv8g0 0/1 Init:ImagePullBackOff 0 7m 10.42.184.43 obriensystemskub0 onap-dcae cdap2-2495595959-fxnmg 0/1 Init:ImagePullBackOff 0 7m 10.42.69.133 obriensystemskub0 onap-dcae dcae-collector-common-event-2687859322-jcv7n 1/1 Running 0 7m 10.42.219.171 obriensystemskub0 onap-dcae dcae-collector-dmaapbc-2087600858-sb98v 1/1 Running 0 7m 10.42.225.93 obriensystemskub0 onap-dcae dcae-controller-1960065296-95xxx 0/1 ContainerCreating 0 7m <none> obriensystemskub0 onap-dcae dcae-pgaas-3690783998-v4w60 0/1 ImagePullBackOff 0 7m 10.42.28.81 obriensystemskub0 onap-dcae dcae-ves-collector-1184035059-t0t7s 0/1 ImagePullBackOff 0 7m 10.42.223.26 obriensystemskub0 onap-dcae dmaap-3637563410-2s7b2 0/1 CrashLoopBackOff 6 7m 10.42.7.93 obriensystemskub0 onap-dcae kafka-2923495538-tb218 0/1 CrashLoopBackOff 6 7m 10.42.49.109 obriensystemskub0 onap-dcae zookeeper-2122426841-2n6h5 1/1 Running 0 7m 10.42.192.205 obriensystemskub0 root@obriensystemskub0:~/oom/kubernetes/oneclick# kubectl get services --all-namespaces -o wide | grep dcae onap-dcae dcae-collector-common-event 10.43.97.177 <nodes> 8080:30236/TCP,8443:30237/TCP,9999:30238/TCP 8m app=dcae-collector-common-event onap-dcae dcae-collector-dmaapbc 10.43.100.153 <nodes> 8080:30239/TCP,8443:30240/TCP 8m app=dcae-collector-dmaapbc onap-dcae dcae-controller 10.43.117.220 <nodes> 8000:30234/TCP,9998:30235/TCP 7m app=dcae-controller onap-dcae dcae-ves-collector 10.43.215.194 <nodes> 8080:30241/TCP,9999:30242/TCP 8m app=dcae-ves-collector onap-dcae zldciad4vipstg00 10.43.110.169 <nodes> 5432:30245/TCP 8m app=dcae-pgaas |
|---|
Pushing Docker Images to ONAP
Other projects have a docker-maven-plugin - need to see if I can run this locally.
Questions
https://lists.onap.org/pipermail/onap-discuss/2017-July/002084.html
Links
https://kubernetes.io/docs/user-guide/kubectl-cheatsheet/
Reference Reviews
https://gerrit.onap.org/r/#/c/6179/
https://gerrit.onap.org/r/#/c/9849/
https://gerrit.onap.org/r/#/c/9839/
Content to edit/merge
Test HD, Network, CPU limits 20170831 1.1 on 64 thread, 256G ram M4.16xLarge spot AWS instance root@ip-172-31-90-90:~/oom/kubernetes/oneclick# free total used free shared buff/cache available Mem: 264141232 41043272 182430348 23300 40667612 221154848 Swap: 0 0 0
root@ip-172-31-90-90:~/oom/kubernetes/oneclick# kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system heapster-4285517626-44q27 1/1 Running 1 33m kube-system kube-dns-2514474280-1fj2x 3/3 Running 3 33m kube-system kubernetes-dashboard-716739405-58j8n 1/1 Running 1 33m kube-system monitoring-grafana-3552275057-wtsp1 1/1 Running 1 33m kube-system monitoring-influxdb-4110454889-9z77v 1/1 Running 2 33m kube-system tiller-deploy-737598192-ckxzh 1/1 Running 1 33m onap-aai aai-dmaap-522748218-r033b 0/1 CrashLoopBackOff 4 28m onap-aai aai-kafka-2485280328-3l3kb 1/1 Running 0 28m onap-aai aai-resources-353718113-cf2wf 0/1 CrashLoopBackOff 5 29m onap-aai aai-service-3321436576-q949v 0/1 Init:0/1 1 29m onap-aai aai-traversal-338636328-rh7f1 0/1 Running 6 29m onap-aai aai-zookeeper-1010977228-s8shl 1/1 Running 0 28m onap-aai data-router-1397019010-jzwcf 0/1 Running 6 29m onap-aai elasticsearch-2660384851-dt9l5 0/1 CrashLoopBackOff 5 28m onap-aai gremlin-3971586470-n7nwf 0/1 Running 4 29m onap-aai hbase-3880914143-n2wl9 1/1 Running 0 28m onap-aai model-loader-service-226363973-31mz4 1/1 Running 6 28m onap-aai search-data-service-1212351515-4jwx0 0/1 Running 6 28m onap-aai sparky-be-2088640323-hsmr2 0/1 Running 6 28m onap-appc appc-1972362106-z1l3l 1/1 Running 0 29m onap-appc appc-dbhost-2280647936-l6vf2 1/1 Running 0 29m onap-appc appc-dgbuilder-2616852186-6smn8 1/1 Running 0 29m onap-message-router dmaap-3565545912-zg8bk 1/1 Running 0 29m onap-message-router global-kafka-701218468-x8dfw 1/1 Running 0 29m onap-message-router zookeeper-555686225-gxthp 1/1 Running 0 29m onap-mso mariadb-2814112212-l81dv 1/1 Running 0 29m onap-mso mso-2505152907-67h4v 1/1 Running 0 29m onap-policy brmsgw-362208961-s2rj4 1/1 Running 0 29m onap-policy drools-3066421234-01v0f 0/1 Running 0 29m onap-policy mariadb-2520934092-g0sbg 1/1 Running 0 29m onap-policy nexus-3248078429-scl7v 1/1 Running 0 29m onap-policy pap-4199568361-6lz2t 1/1 Running 0 29m onap-policy pdp-785329082-vfff9 1/1 Running 0 29m onap-policy pypdp-3381312488-q940q 1/1 Running 0 29m onap-portal portalapps-2799319019-472pl 1/1 Running 0 29m onap-portal portaldb-1564561994-ztnl3 1/1 Running 0 29m onap-portal portalwidgets-1728801515-mm3jj 1/1 Running 0 29m onap-portal vnc-portal-700404418-pkcsc 0/1 Init:2/5 1 29m onap-robot robot-349535534-8g1r5 1/1 Running 0 29m onap-sdc sdc-be-628593118-ptmjx 0/1 Running 0 28m onap-sdc sdc-cs-2640808243-sp59x 1/1 Running 0 28m onap-sdc sdc-es-227943957-qx9vp 1/1 Running 0 28m onap-sdc sdc-fe-1609420241-x10vv 0/1 Init:0/1 1 28m onap-sdc sdc-kb-1998598941-qv76s 1/1 Running 0 28m onap-sdnc sdnc-250717546-zkdzr 1/1 Running 0 29m onap-sdnc sdnc-dbhost-3807967487-b40tg 1/1 Running 0 29m onap-sdnc sdnc-dgbuilder-3446959187-q9tmg 1/1 Running 0 29m onap-sdnc sdnc-portal-4253352894-lrffp 1/1 Running 0 29m onap-vid vid-mariadb-2932072366-gw6b7 1/1 Running 0 29m onap-vid vid-server-377438368-bt6zg 1/1 Running 0 29m |
|---|
