Automate devstack-ovn development setup

[Sebastien Dupont]

Automate the setup described here http://docs.openstack.org/developer/networking-ovn/testing.html#single-node-test-environment and here http://blog.russellbryant.net/2015/05/14/an-ez-bake-ovn-for-openstack/

This would create a 3 nodes devstack (controller + two compute), where OVN is used as the Open vSwitch backend.

Vagrant allows to configure the provider on which the virtual machines are created. Virtualbox is the default provider used to launch the VM's on a developer computer, but other providers can also be used: VMWare, AWS, Openstack, containers stuff, ...

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/228543

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/228543
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=255d5f752a724ea097d081dccf1ee767b2342921
Submitter: Jenkins
Branch: master

commit 255d5f752a724ea097d081dccf1ee767b2342921
Author: Sebastien Dupont <email address hidden>
Date: Mon Sep 28 19:29:20 2015 +0200

    Automated setup using Vagrant + Virtualbox

    Automate the setup described in the devstack test instructions.

    This will create a 2 nodes devstack (controller + compute),
    where OVN is used as the Open vSwitch backend.

    Change-Id: I6d6f77c8d19e4496c1c4f516d403410dd2799009
    Related-Bug: #1499917

[Kyle Mestery (mestery)]

Updating this bug to reference building a 3-node Vagrant setup.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/241455

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/241455
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=2c53618110658df7ceff490b0ff27948c93da703
Submitter: Jenkins
Branch: master

commit 2c53618110658df7ceff490b0ff27948c93da703
Author: Kyle Mestery <email address hidden>
Date: Wed Nov 4 02:55:52 2015 +0000

    Update Vagrant configuration to deploy 3-node OVN setup

    This updates the Vagrant setup to deploy a 3-node Ubuntu Trusty
    setup (1 control node, 2 compute nodes). The Vivid image this
    was previously trying to download was HUGE, and it's not clear
    why running on Vivid is better considering the gate uses
    Trusty.

    Also, adjust the names of the nodes this spawns to be a bit
    more sane. They are now spawned as:

    ovn-controller
    ovn-compute1
    ovn-compute2

    One final change adds some additional configuration into
    local.conf which allows this all to come up and run.

    Closes-Bug: #1499917
    Change-Id: Ife6cfbe18ea1053ca52b8ff0f074987c178a713c
    Signed-off-by: Kyle Mestery <email address hidden>