networking-ovn

  1. Bug #1499917
  2. Comment #5

Comment 5 for bug 1499917

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (master)

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>