Activity log for bug #1505631

Date Who What changed Old value New value Message
2015-10-13 11:21:42 vikram.choudhary bug added bug
2015-10-13 11:21:58 vikram.choudhary neutron: assignee vikram.choudhary (vikschw)
2015-10-13 13:12:41 Ihar Hrachyshka neutron: status New Confirmed
2015-10-13 13:12:44 Ihar Hrachyshka neutron: importance Undecided Wishlist
2015-10-13 13:12:52 Ihar Hrachyshka tags rfe ovs qos rfe
2015-10-19 10:52:05 David Shaughnessy bug added subscriber David Shaughnessy
2015-12-22 02:16:33 Armando Migliaccio neutron: status Confirmed Triaged
2016-01-08 05:13:15 vikram.choudhary neutron: assignee vikram.choudhary (vikschw)
2016-01-12 18:09:25 Armando Migliaccio neutron: status Triaged Incomplete
2016-01-21 08:48:17 Reedip neutron: assignee Reedip (reedip-banerjee)
2016-01-21 08:55:13 vikram.choudhary description [Overview] The IEEE 802.1p signaling standard defines traffic prioritization at Layer 2 of the OSI model. Layer 2 network devices, such as switches, that adhere to this standard can group incoming packets into separate traffic classes.The 802.1p standard is used to prioritize packets as they traverse a network segment (subnet).When a subnet becomes congested, causing a Layer 2 network device to drop packets, the packets marked for higher priority receive preferential treatment and are serviced before packets with lower priorities. The 802.1p priority markings for a packet are appended to the MAC header.On Ethernet networks, 802.1p priority markings are carried in Virtual Local Area Network (VLAN) tags. The IEEE 802.1q standard defines VLANs and VLAN tags. This standard specifies a 3-bit field for priority in the VLAN tag, but it does not define the values for the field. The 802.1p standard defines the values for the priority field. This standard defines eight priority classes (0 - 7). Network administrators can determine the actual mappings, but the standard makes general recommendations. The VLAN tag is placed inside the Ethernet header, between the source address and either the Length field (for an IEEE 802.3 frame) or the EtherType field (for an Ethernet II frame) in the MAC header. The 802.1p marking determines the service level that a packet receives when it crosses an 802.1p-enabled network segment. [Proposal] Existing QoS [1]_ framework can be extend for supporting VLAN priority. [Benefits] - Enhancement to the existing QoS functionality. [What is the enhancement?] - Add VLAN tagging support to the QoS extension. - Add additional command lines for realizing ECN functionality. - Add OVS support. [Related information] [1] QoS https://review.openstack.org/#/c/88599/ [2] Specification https://blueprints.launchpad.net/neutron/+spec/vlan-802.1p-qos [Overview] The IEEE 802.1p signaling standard defines traffic prioritization at Layer 2 of the OSI model. Layer 2 network devices, such as switches, that adhere to this standard can group incoming packets into separate traffic classes.The 802.1p standard is used to prioritize packets as they traverse a network segment (subnet).When a subnet becomes congested, causing a Layer 2 network device to drop packets, the packets marked for higher priority receive preferential treatment and are serviced before packets with lower priorities. The 802.1p priority markings for a packet are appended to the MAC header.On Ethernet networks, 802.1p priority markings are carried in Virtual Local Area Network (VLAN) tags. The IEEE 802.1q standard defines VLANs and VLAN tags. This standard specifies a 3-bit field for priority in the VLAN tag, but it does not define the values for the field. The 802.1p standard defines the values for the priority field. This standard defines eight priority classes (0 - 7). Network administrators can determine the actual mappings, but the standard makes general recommendations. The VLAN tag is placed inside the Ethernet header, between the source address and either the Length field (for an IEEE 802.3 frame) or the EtherType field (for an Ethernet II frame) in the MAC header. The 802.1p marking determines the service level that a packet receives when it crosses an 802.1p-enabled network segment. [Proposal] Existing QoS [1]_ framework can be extend for supporting VLAN priority. This requirement mainly focus provider networks. Note: For the tenant network it can only work if the traffic is segmented via VLANs and does nothing for other type of segmentation. [Benefits] - Enhancement to the existing QoS functionality. [What is the enhancement?] - Add VLAN tagging support to the QoS extension for provider's network. - Add additional command lines for realizing Vlan tag support. - Add OVS support. [Related information] [1] QoS    https://review.openstack.org/#/c/88599/ [2] Specification     https://blueprints.launchpad.net/neutron/+spec/vlan-802.1p-qos
2016-01-27 10:41:35 vikram.choudhary neutron: status Incomplete New
2016-01-27 14:49:47 Miguel Angel Ajo summary QoS VLAN 802.1p Support [RFE] QoS VLAN 802.1p Support
2016-02-11 19:40:07 Armando Migliaccio neutron: status New Confirmed
2016-06-16 22:08:54 Assaf Muller neutron: assignee Reedip (reedip-banerjee)
2016-06-17 04:41:26 Reedip neutron: assignee Reedip (reedip-banerjee)
2016-06-24 18:09:13 Kannan Raman neutron: assignee Reedip (reedip-banerjee) Kannan Raman (kannanrc20)
2016-06-24 18:09:21 Kannan Raman neutron: status Confirmed In Progress
2016-06-30 18:17:32 Armando Migliaccio neutron: status In Progress Confirmed
2016-06-30 18:38:39 Armando Migliaccio tags ovs qos rfe ovs qos rfe-postponed
2017-01-31 15:51:13 Reedip neutron: assignee Kannan Raman (kannanrc20) Reedip (reedip-banerjee)
2017-07-10 14:40:25 Ann Taraday bug added subscriber Ann Taraday
2022-11-08 10:57:53 Lajos Katona neutron: status Confirmed Won't Fix