openstack
/
kuryr-libnetwork
Code Issues Proposed changes
kuryr-libnetwork/contrib/vagrant
History
Kyle Mestery 99897cc1cc Cleanups to Vagrant documentation and scripts 
Fix some spelling errors in the scripts and the Vagrant documentation.
Also, add a note about creating the default subnetpool in the Vagrant
documentation.

Change-Id: I13454328d7b4372d6773661b006466f3419c4fe0
Signed-off-by: Kyle Mestery <mestery@mestery.com>
 		2015-11-20 13:36:51 -06:00
..
config Add files to enable demo kuryr setup using Vagrant 2015-10-08 20:40:00 +05:30
README.md Cleanups to Vagrant documentation and scripts 2015-11-20 13:36:51 -06:00
Vagrantfile Refactor Vagrantfile to allow other providers 2015-11-19 13:18:45 +01:00
devstack.sh Add files to enable demo kuryr setup using Vagrant 2015-10-08 20:40:00 +05:30
docker.sh Update vagrant support to use docker 1.9.0 rather experimental 2015-10-19 10:43:42 +05:30
install_kuryr.sh Add files to enable demo kuryr setup using Vagrant 2015-10-08 20:40:00 +05:30
vagrant.sh Add files to enable demo kuryr setup using Vagrant 2015-10-08 20:40:00 +05:30

README.md

vagrant-devstack-Kuryr

A Vagrant based kuryr,neutron,keystone and experimental docker system. Steps to try vagrant image:

  1. Install virtual-box and vagrant on your local machine.
  2. Git clone kuryr repository.
  3. cd kuryr/contrib/vagrant
  4. vagrant up It will take around 10 mins.
  5. vagrant ssh You will get vm shell with keystone and neutron already running.
  6. cd kuryr && ./scripts/run_kuryr.sh & Kuryr service will be up and listening on port 2377.
  7. Create the default kuryr subnetpool: neutron subnetpool-create --default-prefixlen 24 --pool-prefix 10.10.0.0/16 kuryr

At this point you should have experimental docker, kuryr, neutron, keystone all up, running and pointing to each other. Any docker network related commands can be tried now as explained in [1].

References: [1] https://github.com/openstack/kuryr/blob/master/doc/source/devref/libnetwork_remote_driver_design.rst#L64