Inherit segmentation details for trunk subports if requested
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Boden R |
Bug Description
https:/
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit 4a6d06550bd98b4
Author: Armando Migliaccio <email address hidden>
Date: Tue Feb 21 18:43:38 2017 -0800
Inherit segmentation details for trunk subports if requested
This patch introduces support for requests where the user does
not know the segmentation details of a subport and by specifying
segmentatio
details from the network to which the subport is connected to, thus
ignoring the segmentation_id in case it were to be specified.
This type of request is currently expected to have correct results
when the network segmentation type is 'vlan', and the network has
only one segment (provider-net extension use case).
DocImpact: Extend trunk documentation to include Ironic use case.
Closes-bug: #1648129
Depends-on: Ib510aade1716e6
Change-Id: I3be2638fddf3a9
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Low |
assignee: | nobody → Boden R (boden) |
Fix proposed to branch: master /review. openstack. org/501876
Review: https:/