Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1622233

Summary: [RFE] Add Trunk port Support
Product: Red Hat OpenStack Reporter: Dan Radez <dradez>
Component: python-networking-ansibleAssignee: Dan Radez <dradez>
Status: CLOSED ERRATA QA Contact: Arkady Shtempler <ashtempl>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.0 (Train)CC: amuller, bfournie, ccopello, dvd, gregraka, jamsmith, jlibosva, jzaher, michapma, mlammon, racedoro, sclewis, scohen, tfreger
Target Milestone: Upstream M2Keywords: FutureFeature, TechPreview, Triaged
Target Release: 16.0 (Train on RHEL 8.1)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-networking-ansible-3.0.0-0.20191031151708.25d3a4e.el8 Doc Type: Technology Preview
Doc Text:
In Red Hat OpenStack Platform 16.0, a technology preview has been added to modify switch ports to put them into trunking mode and assign more than one VLAN to them.
Story Points: ---
Clone Of:
: 1753248 (view as bug list) Environment:
Last Closed: 2020-02-06 14:37:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1774863    
Bug Blocks: 1622235, 1753248, 1776858    

Description Dan Radez 2018-08-24 20:27:02 UTC
Future use cases will need to be able to modify switch ports to put them into trunking mode and assign more than one vlan to them. Investigation needs to happen to understand how to represent this in neutron in a way that can be passed to ML2 to apply trunk configs to a port.

Comment 4 Toni Freger 2018-12-26 08:59:47 UTC
Following the recent decision to backport ansible-networking project to OSP13, which will add additional work.
It was agreed by Ramon, Assaf and myself that we will remove the QE ack from all OSP15 RFEs, and re-plan it.

Comment 21 errata-xmlrpc 2020-02-06 14:37:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:0283