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
segmentation_type=inherit will let the trunk plugin infer these
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.
Reviewed: https:/ /review. openstack. org/436756 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=4a6d06550bd 98b473bdcf5e58d cfb7f5ca9424ef
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4a6d06550bd98b4 73bdcf5e58dcfb7 f5ca9424ef
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 n_type= inherit will let the trunk plugin infer these
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 ca92940b85245ed a7d0c84a070 723dd852a3f9ea9 f64eb1d0dd6
Change-Id: I3be2638fddf3a9