Deploy non-ONAP development OpenStack environment for VNF testing

[taylor]

Goal: Segment testing of non-ONAP VNF work from ONAP

This is Part 2: Get VNFs running on OpenStack without ONAP from https://docs.google.com/document/d/1GrdMynJA738fmkOPvTrkZAGz04eC4TcvmLRYLW4wbCs/edit#

• Provision new packet server - cnfs-dev02 => https://app.packet.net/devices/26702938-4b18-4e4f-af7c-89926925729a

  • m1.xlarge.x86 - Memory: 256 GB, CPU: Intel Xeon E5-2650 (2x) x86 24 Cores @ 2.2 GHz, Disk: 2.8 TB
  • Public 147.75.100.181, 147.75.100.180
  • Private 10.80.130.3, 10.80.130.2

• Add dns pointing to 147.75.100.181

• Provision base dev software and pull down onap-demo code

• Deploy openstack to new packet server using working vagrant setup => https://github.com/cncf/onap-demo/tree/amsterdam-openstack-ocata/vagrant

[taylor]

Setting up OpenStack Ocata in Virtualbox on Ubuntu 17.10

Provision base dev software and pull down onap-demo code:

git clone git@github.com:cncf/onap-demo.git -b amsterdam-openstack-ocata

cd onap-demo

./vagrant/run_demo.sh

Deploy the router to new packet server:

cd router-node ; vagrant plugin install vagrant-reload ; vagrant up

Deploy openstack to new packet server:

cd ../vagrant ; vagrant up control ; vagrant up control-1 ; vagrant up control-2

Register compute nodes as resources for OpenStack to use:

vagrant ssh control -- source /vagrant/openrc \; nova-manage cell_v2 simple_cell_setup