Packstack OPNFV Sandbox

This OPNFV SandBox is intended to be a laptop compatible dev environment. It is currently under development. Get involved, download it and help evaluate, debug and improve! https://github.com/Aricg/PackStackSandBox

SandBox currently exists as a template for further sandbox work with packstack, it brings up two nodes on a machine with at least 6GB of memory. One controller and One Compute/Networking node. It is intended to be easy to modify to meet our/your needs.

Nat networking will provide the gateway to the internet as well as connectivity between hosts throught the vboxnetX interface created by vagrant

Setup Masquerade/Forwarding on your host to you vboxnet interface

Linux:

make sure these are set in /etc/sysctl.d

net.ipv4.ip_forward = 1
net.ipv4.conf.all.proxy_arp = 1

And loaded

sudo sysctl -p

In my example my hosts interface for internet connetiviy is docker0 (yours might be eth0 for example) and my the vboxnet brought up by vagrant up is vboxnet4 and the subnet I have set for the sandbox machines in the vagrantfile.yaml is 10.0.20.0/22

If you are able to configure and use a bridge we can bring up openstack VMs on your local network. you will need a netmask of 23 or below.

My bridge in this readme is called docker0

$ brctl show
bridge name bridge id STP enabled interfaces
docker0

To start copy Vagrantfile.yml.template.bridgemode to Vagrantfile.yml to reflect the network avaliable to you. In this example I have a /22 avaliable on my home network, Later we reserve a /24 section of my /22 network for the neutron router we create.

netmask: netmask of your private subnet, probably given to you via dhcp. you can see this with ifconfig, however on osx if will be in the unreadble format, something like 0xffffff00 Refer here for a table that human can read. http://www.pawprint.net/designresources/netmask-converter.php Most home networks only give out a /24 you will need to log into your router and change your range to at least a /23 so that we an properly route to the router that neutron creates.

gateway: For bridged mode Your workstations gateway to the internet (your routers ip, this is also the ip you go to to increase your network size ) you can check this with ip r on linux or netstat -nr on osx For nat mode set this to the first ip in the range you are choosing for private_ip

neutron_router_start: This will be the start of your openstack dhcp, I also use this as your neutron router gateway. give neutron its own /24 range

neutron_router_end: the end of the range explained above

controller:

bridged_ip:* this interface should be given an ip on the same /24 as your workstation.

private_ip:* this interface can have any ip you want, virtualbox deals with the routing.

compute:

bridged_ip:* same rules as the controller bridged_ip but unique

private_ip:* same rules as controller: private_ip but unique

for nat mode set the bridged_ip and private_ip to the same values for each host (as seen in Vagrantfile.yml.template.natmode)

the answerfile is generated from ans.template or ans.NAT.template when you run vagrant up. packstack should now prompt you for the root password of both nodes. The password is "vagrant" if packstack fails for some reason, just run it again.

Networking

To setup networking, and launch the cirros minimal VM you must wait for the above operations to complete. (packstack and copying the keystonerc_admin) Once those are done, vagrant ssh into the networking (compute node):