add property to configure provider networks

Bug #1694726 reported by Vladislav Belogrudov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Undecided
Vladislav Belogrudov

Bug Description

currently it is not easy to tell if provider networks are to be used or not. Depending on that one could configure non-DVR computes for direct connections of instances to provider networks.

Changed in kolla-ansible:
assignee: nobody → Vladislav Belogrudov (vlad-belogrudov)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)

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

Changed in kolla-ansible:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/469529
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=f6eefdf38860928ebbccca9eb40dfb0db4f0de1a
Submitter: Jenkins
Branch: master

commit f6eefdf38860928ebbccca9eb40dfb0db4f0de1a
Author: Vladislav Belogrudov <email address hidden>
Date: Wed May 31 17:51:09 2017 +0300

    Add flag to allow provider networks

    In case of provider networks we need to configure external bridge
    on compute nodes, like it is done in DVR. The only way to tell
    if provider networks are to be used is a new flag.

    Change-Id: I1aef197ee2b84e28f2131f058e6995551f873fe1
    Closes-Bug: #1694726

Changed in kolla-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 5.0.0.0b3

This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.