NsxV3: external network support

Bug #1493682 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vmware-nsx
Fix Released
Undecided
Unassigned

Bug Description

https://review.openstack.org/208779

Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/vmware-nsx" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 7e2205e9ab294aa328a9c07ef5950d7b3a84c5b3
Author: linb <email address hidden>
Date: Mon Aug 3 15:01:43 2015 +0800

    NsxV3: external network support

    external network is attached to default tier0 router by default, else
    attached to tier0 via --provider:physical_network

    DocImpact
    Change-Id: I3fa4e1a6955d47f68f86b36f214ce4a43daefe5b

Tags: vmware-nsx
Lana (loquacity)
affects: openstack-manuals → vmware-nsx
Adit Sarfaty (asarfaty)
Changed in vmware-nsx:
status: New → Fix Committed
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.