yahoo-eng-team team mailing list archive

[OpenStack Infra <1679999@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/502108
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bc5ca57910c1bd6bbe8320dc67ab086a00a9eb39
Submitter: Jenkins
Branch:    master

commit bc5ca57910c1bd6bbe8320dc67ab086a00a9eb39
Author: Boden R <bodenvmw@xxxxxxxxx>
Date:   Fri Sep 8 09:51:18 2017 -0600

    doc inherit segmentation type for trunking
    
    This patch updates our docs to include some details on the 'inherit'
    segmentation type supported by trunk subports. The API is updated in
    I0772463d71cbb6703345e66f52ad6c02163a00ff.
    
    Change-Id: I9bebf8a3543bff43cf6e80a0d4523b0c9b5c6eb5
    Closes-Bug: #1679999


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1679999

Title:
      Inherit segmentation details for trunk subports if requested

Status in neutron:
  Fix Released

Bug description:
  https://review.openstack.org/436756
  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 4a6d06550bd98b473bdcf5e58dcfb7f5ca9424ef
  Author: Armando Migliaccio <armamig@xxxxxxxxx>
  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
      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.
      
      Closes-bug: #1648129
      
      Depends-on: Ib510aade1716e6ca92940b85245eda7d0c84a070
      Change-Id: I3be2638fddf3a9723dd852a3f9ea9f64eb1d0dd6

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1679999/+subscriptions