Bug 1550668

Summary: [RFE] [ODL] Add support for DSCP marking with VXLAN encapsulation
Product: Red Hat OpenStack Reporter: Tim Rozet <trozet>
Component: openstack-tripleo-heat-templatesAssignee: Janki <jchhatba>
Status: CLOSED ERRATA QA Contact: Yariv <yrachman>
Severity: high Docs Contact:
Priority: high    
Version: 14.0 (Rocky)CC: atelang, fbaudin, jchhatba, joflynn, ltomasbo, mariel, mburns, mkolesni, nyechiel, rhel-osp-director-maint, trozet
Target Milestone: Upstream M2Keywords: FutureFeature, TechPreview, Triaged
Target Release: 14.0 (Rocky)Flags: jchhatba: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-9.0.0-0.20180710202746.d2994ca.el7ost Doc Type: Technology Preview
Doc Text:
This feature enables forwarding tenant traffic based on DSCP marking from tenants encapsulated in the VXLAN IP header. This feature is a technology preview for OSP14.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:48:58 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: 1329358    
Bug Blocks: 1420173, 1476900, 1615661, 1624217    

Description Tim Rozet 2018-03-01 18:36:36 UTC
Description of problem:
This requirement is to support DSCP inheritance from tenant traffic to VXLAN headers in VXLAN tunnel overlays.  The DSCP bits should be copied from the inner header to the outer header.

OpenDaylight already has support to configure this globally for every switch.  There needs to be a way to enable/disable this functionality via TripleO.

Comment 2 Nir Yechiel 2018-03-18 00:02:10 UTC
*** Bug 1399234 has been marked as a duplicate of this bug. ***

Comment 4 Tim Rozet 2018-05-24 18:36:05 UTC
Moving back to ON_DEV as there is no patch merged upstream into THT that enables this feature (only in puppet-odl)

Comment 18 errata-xmlrpc 2019-01-11 11:48:58 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-2019:0045