[FLOC-3017] Allow run-acceptance-tests to boot devstack guests

[wallrj]

Design / Partial implementation for: https://clusterhq.atlassian.net/browse/FLOC-3017

TODO

• Figure out how to get libcloud to wait for public IP of instance on Rackspace and private IP on devstack, OR
• Figure out how to assign public IPs on devstack (needn't be actual public IPs, maybe just so called floating IPs)
• devstack guests need to be able to access the internet but can't without some nat IPtables rules on the devstack host. We'd been adding the rules individually for each guest but perhaps somethign like iptables -t nat -I POSTROUTING --source 10.0.0.0/8 -j MASQUERADE will do the trick.

[wallrj]

It kind of works:

./admin/run-acceptance-tests --no-pull --distribution=ubuntu-14.04 --provider=openstack --dataset-backend=devstack-openstack --config-file=$PWD/config.yml --branch=master --flocker-version='' flocker.acceptance.endtoend.test_dataset
...

[[email protected]]: If you would like to use Docker as a non-root user, you should now consider
[[email protected]]: adding your user to the "docker" group with something like:
[[email protected]]: 
[[email protected]]:   sudo usermod -aG docker ubuntu
[[email protected]]: 
[[email protected]]: Remember that you will have to log out and back in for this to take effect!
[[email protected]]: 
[[email protected]]: Running apt-get update
[[email protected]]: E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
[[email protected]]: E: Unable to lock directory /var/lib/apt/lists/
[[email protected]]: E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
[[email protected]]: E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
Destroying acceptance-test-richardw-0
Destroying acceptance-test-richardw-1


...

And iptables -t nat -I POSTROUTING --source 10.0.0.0/8 -j MASQUERADE allows new guests to access the internet.

[tomprince]

I'd avoid say all, just some other than rackspace.

[tomprince]

I think the right solution is to enable floating IPs. Or, better but I don't know if it is possible, mark the fixed IPs that are assigned as public, rather than private.