openstack
/
kuryr-libnetwork
Code Issues Proposed changes
kuryr-libnetwork/contrib/vagrant
History
Liping Mao (limao) ea12e966ee Fix vagrant up with ubuntu/xenial64 
There is the following bug in ubuntu/xenial64 cloud image.
https://bugs.launchpad.net/cloud-images/+bug/1569237
This will cause that vagrant user will not exist.

Change-Id: Iacc4135fa165d8624ad61c4e5170683180234cbf
Closes-Bug: #1687197
 		2017-05-07 14:14:46 +08:00
..
config Docker Daemon should use port 2375 instead of 23750 at some places 2016-09-08 13:35:12 +05:30
README.md Vagrant: Fix example for OVN 2016-10-24 09:41:24 -05:00
Vagrantfile Fix vagrant up with ubuntu/xenial64 2017-05-07 14:14:46 +08:00
add_vagrant_user.sh Fix vagrant up with ubuntu/xenial64 2017-05-07 14:14:46 +08:00
devstack.sh Allow for user specified local.conf changes with Vagrant 2015-12-28 15:34:18 -06:00
vagrant.sh OS_HOST_IP is not working, replacing with HOST_IP 2016-12-07 08:13:21 +05:30

README.md

vagrant-devstack-Kuryr-libnetwork

Getting started

A Vagrant based kuryr,neutron,keystone and experimental docker system.

Steps to try vagrant image:

  1. Install Vagrant on your local machine. Install one of the current providers supported: VirtualBox, Libvirt or Vagrant
  2. Git clone kuryr-libnetwork repository.
  3. Run cd kuryr-libnetwork/contrib/vagrant
  4. Run vagrant up It will take from 10 to 60 minutes, depending on your internet speed. Vagrant-cachier can speed up the process [2].
  5. vagrant ssh You will get a VM with everything running. You will get vm shell with keystone and neutron already running.

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 [2] http://fgrehm.viewdocs.io/vagrant-cachier/

Vagrant Options available

You can set the following environment variables before running vagrant up to modify the definition of the Virtual Machine spawned:

  • VAGRANT_KURYR_VM_BOX: To change the Vagrant Box used. Should be available in atlas.

    export VAGRANT_KURYR_VM_BOX=centos/7

    Could be an example of a rpm-based option.

  • VAGRANT_KURYR_VM_MEMORY: To modify the RAM of the VM. Defaulted to: 4096

  • VAGRANT_KURYR_VM_CPU: To modify the cpus of the VM. Defaulted to: 2

  • VAGRANT_KURYR_RUN_DEVSTACK: Whether vagrant up should run devstack to have an environment ready to use. Set it to 'false' if you want to edit local.conf before run ./stack.sh manually in the VM. Defaulted to: true. See below for additional options for editing local.conf.

Additional devstack configuration

To add additional configuration to local.conf before the VM is provisioned, you can create a file called "user_local.conf" in the contrib/vagrant directory of networking-kuryr. This file will be appended to the "local.conf" created during the Vagrant provisioning.

For example, to use OVN as the Neutron plugin with Kuryr, you can create a "user_local.conf" with the following configuration:

enable_plugin networking-ovn http://git.openstack.org/openstack/networking-ovn
enable_service ovn-northd
enable_service ovn-controller
disable_service q-agt
disable_service q-l3
disable_service q-dhcp