NSX-mh: honour distributed_router config flag

Bug #1483920 reported by Salvatore Orlando
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Invalid
Undecided
Unassigned
Juno
Fix Released
Undecided
Salvatore Orlando
vmware-nsx
Fix Released
Undecided
Salvatore Orlando

Bug Description

The VMware NSX plugin is not honoring the "router_distributed = True" flag when set in /etc/neutron.conf. If the router_distributed parameter is set to "True", this should result in all routers that are created by tenants to default to distributed routers. For example, the below CLI command should create a distributed logical router, but instead it creates a non-distributed router.

neutron router-create --tenant-id $TENANT tenant-router

In order to create a distributed router the "--distributed True" option must be passed, as show below.

neutron router-create --tenant-id $TENANT csinfra-router-test --distributed True

This happens because the NSX-mh plugin relies on the default value implemented in the backend rather than in the neutron configuration and should be changed to ensure this plugin behaves like the reference implementation

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to vmware-nsx (master)

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

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

Reviewed: https://review.openstack.org/211774
Committed: https://git.openstack.org/cgit/openstack/vmware-nsx/commit/?id=0649bb61f97f9a24dda525ec02a8f531914ae02c
Submitter: Jenkins
Branch: master

commit 0649bb61f97f9a24dda525ec02a8f531914ae02c
Author: Salvatore Orlando <email address hidden>
Date: Tue Aug 11 15:54:03 2015 -0700

    NSX-mh: use router_distributed flag

    Even if the plugin technically already leverages this flag as it's
    used in the l3_dvr_db mixin, the logic for the NSX-mh implies that
    it is the backend that decides whether routers by default are
    centralized or distributed.

    This patches changes the logic for the default value for distributed
    routers, ensuting the router_distributed flag is honoured.

    Change-Id: I6cee010622d310477867b94b754aa2260b43b879
    Closes-Bug: #1483920

Changed in vmware-nsx:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to vmware-nsx (stable/kilo)

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/213092

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to vmware-nsx (stable/kilo)

Reviewed: https://review.openstack.org/213092
Committed: https://git.openstack.org/cgit/openstack/vmware-nsx/commit/?id=8fce2bc969c6554e7e892ead9ef8bd4b8437d941
Submitter: Jenkins
Branch: stable/kilo

commit 8fce2bc969c6554e7e892ead9ef8bd4b8437d941
Author: Salvatore Orlando <email address hidden>
Date: Tue Aug 11 15:54:03 2015 -0700

    NSX-mh: use router_distributed flag

    Even if the plugin technically already leverages this flag as it's
    used in the l3_dvr_db mixin, the logic for the NSX-mh implies that
    it is the backend that decides whether routers by default are
    centralized or distributed.

    This patches changes the logic for the default value for distributed
    routers, ensuting the router_distributed flag is honoured.

    Cherry-picked from commit: 0649bb61f97f9a24dda525ec02a8f531914ae02
    Change-Id: I6cee010622d310477867b94b754aa2260b43b879
    Closes-Bug: #1483920

tags: added: in-stable-kilo
Alan Pevec (apevec)
Changed in neutron:
status: New → Invalid
Adit Sarfaty (asarfaty)
Changed in vmware-nsx:
status: Fix Committed → Fix Released
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.