Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add hardware profile

The official documentation for installation of ONAP with OOM / Kubernetes is located in readthedocs here (TBD).  The supported versions of Kubernetes is as follows:

Software Requirements

ReleaseKubernetesHelmKubectlDocker
amsterdam1.7.x2.3.x1.7.x1.12.x
beijing/master1.8.x2.7.x1.8.x17.03-ce

Hardware Requirements

ReleaseRAMHDvCoresPorts
any

59G at startup

70G after 48h


Recommend

128G class VM

75G at startup

100G after a week


Recommend

120-160G HD

4 min

54 peak at startup


recommended

16 vCores

see list on PortProfile



Recommend

0.0.0.0/0 (all open)



Installation Flow

1) To start - pick your infrastructure - ONAP supports deployment to all the major public clouds such as:

...


Details

Table of Contents

Installation templates for Kubernetes and deploying ONAP via OOM for the master and amsterdam branches are in the following locations

...

Kubernetes devops / workarounds / troubleshooting content restored from version 378  - into the page ONAP on Kubernetes on Rancher

Example End to End Kubernetes based ONAP install and deployment

Scenario: installing Rancher on clean Ubuntu 16.04 64g VM (single collocated server/host) and the master branch of onap via OOM deployment (2 scripts)

...

Code Block
wget https://jira.onap.org/secure/attachment/11122/cd.sh
chmod 777 cd.sh
wget https://jira.onap.org/secure/attachment/11124/aaiapisimpledemoopenecomporg.cer
wget https://jira.onap.org/secure/attachment/11125/onap-parameters.yaml
wget https://jira.onap.org/secure/attachment/11126/aai-cloud-region-put.json
./cd.sh -b master
# wait about 25-60 min depending on the speed of your network pulling docker images


Results

Code Block
obrienbiometrics:azure michaelobrien$ ssh ubuntu@cd.onap.info
Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-1041-aws x86_64)
ubuntu@ip-172-31-95-122:~$ sudo su -
root@ip-172-31-95-122:~# history
    1  ls
    2  pwd
    3  history
root@ip-172-31-95-122:~# wget https://jira.onap.org/secure/attachment/11117/oom_rancher_setup.sh
--2018-02-27 15:51:09--  https://jira.onap.org/secure/attachment/11117/oom_rancher_setup.sh
Saving to: ‘oom_rancher_setup.sh’
oom_rancher_setup.sh                        100%[=========================================================================================>]   6.68K  --.-KB/s    in 0s      
root@ip-172-31-95-122:~# chmod 777 oom_rancher_setup.sh 
root@ip-172-31-95-122:~# wget https://jira.onap.org/secure/attachment/11122/cd.sh
--2018-02-27 15:51:22--  https://jira.onap.org/secure/attachment/11122/cd.sh
root@ip-172-31-95-122:~# wget https://jira.onap.org/secure/attachment/11124/aaiapisimpledemoopenecomporg.cer
--2018-02-27 15:51:32--  https://jira.onap.org/secure/attachment/11124/aaiapisimpledemoopenecomporg.cer
root@ip-172-31-95-122:~# wget https://jira.onap.org/secure/attachment/11125/onap-parameters.yaml
--2018-02-27 15:51:37--  https://jira.onap.org/secure/attachment/11125/onap-parameters.yaml
root@ip-172-31-95-122:~# wget https://jira.onap.org/secure/attachment/11126/aai-cloud-region-put.json
--2018-02-27 15:51:42--  https://jira.onap.org/secure/attachment/11126/aai-cloud-region-put.json

root@ip-172-31-95-122:~# ./oom_rancher_setup.sh -b master -s cd.onap.info -e onap
Installing on cd.onap.info for master: Rancher: 1.6.14 Kubectl: 1.8.6 Helm: 2.6.1 Docker: 17.03
+ sh -c docker version
Client: Version:      17.03.2-ce
Status: Downloaded newer image for rancher/server:v1.6.14
Saving to: ‘helm-v2.6.1-linux-amd64.tar.gz’
--2018-02-27 15:52:46--  https://releases.rancher.com/cli/v0.6.7/rancher-linux-amd64-v0.6.7.tar.gz
Get:2 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/universe amd64 jq amd64 1.5+dfsg-1 [144 kB]
Setting up jq (1.5+dfsg-1) ...
publicValue: 896EC0CC76D9A171BFF0 secretValue: wH1x1hf5oJe9FSPLex1rgTkk5oabtRMrJGb9MJ6x
ID        NAME      ORCHESTRATION   STATE     CREATED
1a5       Default   cattle          active    2018-02-27T15:53:04Z
Creating kubernetes environment named onap
env id: 1a7
you should see an additional kubernetes environment
ID        NAME      ORCHESTRATION   STATE     CREATED
1a5       Default   cattle          active    2018-02-27T15:53:04Z
1a7       onap      kubernetes      active    2018-02-27T15:53:48Z
Registering host for image: rancher/agent:v1.2.9 url: http://127.0.0.1:8880/v2-beta/scripts/9E6292FC1B3C65923DD2:1514678400000:Ri3dGEnzBp03z2DVtDrZ4nCQ0XE registrationToken: 9E6292FC1B3C65923DD2:1514678400000:Ri3dGEnzBp03z2DVtDrZ4nCQ0XE
Status: Downloaded newer image for rancher/agent:v1.2.9
INFO: Running Agent Registration Process, CATTLE_URL=http://cd.onap.info:8880/v1
INFO: Attempting to connect to: http://cd.onap.info:8880/v1
INFO: http://cd.onap.info:8880/v1 is accessible
INFO: Launched Rancher Agent: 2a4a71b60657b964701019de36c6045f842d7844057433362f715e201751cf6f
waiting 7 min for host registration to finish
KUBECTL_TOKEN base64 encoded: QmFzaWMgT0RrMlJVTXdRME0zTmtRNVFURTNNVUpHUmpBNmQwZ3hlREZvWmpWdlNtVTVSbE5RVEdWNE1YSm5WR3RyTlc5aFluUlNUWEpLUjJJNVRVbzJlQT09
Verify all pods up on the kubernetes system - will return localhost:8080 until a host is added
kubectl get pods --all-namespaces
NAMESPACE     NAME                                   READY     STATUS    RESTARTS   AGE
kube-system   heapster-76b8cd7b5-bjckj               1/1       Running   0          6m
kube-system   kube-dns-5d7b4487c9-zz9cp              3/3       Running   0          6m
kube-system   kubernetes-dashboard-f9577fffd-tcxld   1/1       Running   0          6m
kube-system   monitoring-grafana-997796fcf-n4sw5     1/1       Running   0          6m
kube-system   monitoring-influxdb-56fdcd96b-h2jr8    1/1       Running   0          6m
kube-system   tiller-deploy-cc96d4f6b-6nlgh          1/1       Running   0          6m


172-31-95-122:~# nohup ./cd.sh -b master &
[1] 21891
root@ip-172-31-95-122:~# nohup: ignoring input and appending output to 'nohup.out'
root@ip-172-31-95-122:~# tail -f nohup.out 
Tue Feb 27 16:43:00 UTC 2018
verify onap-config is 0/1 not 1/1 - as in completed - an error pod - means you are missing onap-parameters.yaml or values are not set in it.
waiting for config pod to complete
pre pull docker images - 15+ min
docker login -u docker -p docker nexus3.onap.org:10001
Login Succeeded
docker pull oomk8s/readiness-check:1.1.0
Status: Downloaded newer image for nexus3.onap.org:10001/openecomp/appc-image:v1.2.0
waiting for last pull
start onap pods
********** Creating deployments for policy ********** 
Creating namespace **********
namespace "onap-policy" created
Creating service account **********
clusterrolebinding "onap-policy-admin-binding" created
Creating registry secret **********
secret "onap-docker-registry-key" created
Creating deployments and services **********
NAME:   onap-policy
LAST DEPLOYED: Tue Feb 27 17:20:31 2018
NAMESPACE: onap
STATUS: DEPLOYED
==> v1/ConfigMap
NAME                                  DATA  AGE
policy-dep-pe-configmap               13    1s
policy-dep-drools-settings-configmap  1     1s
policy-sdk-log-configmap              1     1s
policy-filebeat-configmap             1     1s
policy-pdp-log-configmap              1     1s
policy-drools-log-configmap           1     1s
policy-pap-log-configmap              1     1s

....

8 pending > 0 at the 88th 15 sec interval
onap-aaf              aaf-6c64db8fdd-glxxv                          0/1       Running            0          25m
onap-sdnc             dmaap-listener-579cdfd5cb-wd9gd               0/1       Init:0/1           2          26m
onap-sdnc             sdnc-0                                        0/2       Init:0/1           2          26m
onap-sdnc             sdnc-dbhost-0                                 0/2       Pending            0          26m
onap-sdnc             sdnc-dgbuilder-794d686f78-tgq5t               0/1       Init:0/1           2          26m
onap-sdnc             sdnc-portal-69b79b6646-g7zz2                  0/1       Init:0/1           2          26m
onap-sdnc             ueb-listener-6ff56545b6-754v7                 0/1       Init:0/1           2          26m
onap-vfc              vfc-ztevnfmdriver-585d8db4f7-q24z6            0/1       ImagePullBackOff   0          25m
Basic Policy Health Check                                             | PASS |
root@ip-172-31-95-122:~# kubectl get pods --all-namespaces | grep onap-policy
onap-policy           brmsgw-869dc8888c-htkkz                       1/1       Running            0          1h
onap-policy           drools-5f568559b-vgtd9                        2/2       Running            0          1h
onap-policy           mariadb-7c66956bf-tkszv                       1/1       Running            0          1h
onap-policy           nexus-69f7497db5-rnmt9                        1/1       Running            0          1h
onap-policy           pap-7fbff7db64-fpqgj                          2/2       Running            0          1h
onap-policy           pdp-55c454589-nzfcf                           2/2       Running            0          1h
root@ip-172-31-95-122:~# kubectl get services --all-namespaces | grep onap-policy
onap-policy           brmsgw                       NodePort    10.43.5.29      <none>        9989:30216/TCP                    1h
onap-policy           drools                       NodePort    10.43.96.150    <none>        6969:30217/TCP,9696:30221/TCP     1h
onap-policy           mariadb                      ClusterIP   None            <none>        3306/TCP                          1h
onap-policy           nexus                        ClusterIP   None            <none>        8081/TCP                          1h
onap-policy           pap                          NodePort    10.43.125.137   <none>        8443:30219/TCP,9091:30218/TCP     1h
onap-policy           pdp                          NodePort    10.43.130.155   <none>        8081:30220/TCP                    1h
root@ip-172-31-95-122:~# curl http://cd.onap.info:30220/pdp/swagger-ui.html#/policy-engine-services
<div id="swagger-ui-container" class="swagger-ui-wrap"></div>
root@ip-172-31-95-122:~# 


# will post a curl REST get/post in a minute

...

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 55G 60G ram.

TODO: REMOVE from table cell - wrapping is not working

...