openstack/kuryr
Code Issues Proposed changes
8231541b01
kuryr/contrib/vagrant
History
Vikas Choudhary ab0c782ad6 Update vagrant support to use docker 1.9.0 rather experimental 
Experimental docker changes very frequently and this can lead to unexpected
behavior. It will be better to use docker latest release rather experimental.

Change-Id: Ic40155a3788e37158df65d43bc8629f4f30a7bbf
Closes-bug: #1507447
2015-10-19 10:43:42 +05:30
..
config Add files to enable demo kuryr setup using Vagrant 2015-10-08 20:40:00 +05:30
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
README.md 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
Vagrantfile 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. Intall 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.

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