see (Thanks for the catch Brian Freeman)

https://wiki.onap.org/display/DW/ONAP+on+Kubernetes?focusedCommentId=20087232&refresh=1512611666778#comment-20087232

Brian Freeman

Was able to complete bringing up ONAP on Azure through health check except for dcae

A few things missing:

1. SDNC missing ueb-listener and dmaap-listener since OOM not in sync with sdnc docker-compose.yaml
   1. Will not be able to run vCPE in OOM till this is fixed
2. SDC looks like it is missing the sdc-sanity container (sync with sdc docker-compose.yaml)

Had to add a data disk to the Ubuntu VM.

1. Add a  data disk via azure portal or cli and login - new disk should be /mnt 
   1. create /mnt/onap
   2. create /mnt/docker
   3. create /mnt/dockerdata_nfs
   4. ln -s /mnt/onap /opt/onap
   5. ln -s /mnt/dockerdata_nfs /dockerdata_nfs
2. remove docker engine via apt remove
3. rm /var/lib/docker
4. ln -s /opt/docker /var/lib/docker
   1. this provides disk space for docker images, containers and file system
5. add input ports to network security group
   1. 8880, 4500, 500 and the range 30000 - 31000 
   2. I also opened 8080, 8989 and 10250 but I don't think those are needed
6. Run oom_rancher_setup_1.sh and continue with the WIKI instructions

• Reply
• Like
• less than a minute ago #
  

  Michael O'Brien

Yes forgot to point out the requirements on this page - you will need 70G to install ONAP and it will run up to 90 over a week (mostly logs)

Curious about Azure filesystems - I had issues with non-EBS in the past - will recheck.

Will raise a JIRA on the HEAT to OOM sync for SDNC

for SDC - would raise a JIRA but I don't see the sanity container in HEAT - I see the same 5 containers in both