yahoo-eng-team team mailing list archive

[Nate Johnston <Nate_Johnston@xxxxxxxxxxxxxxxxx>]

We have decided that an alternate methodology is preferable, and will
file a new bug for a fresh RFE.  Changing status on this to 'invalid'
and abandoning the associated changeset.

** Changed in: neutron
       Status: Triaged => Invalid

** Changed in: neutron
     Assignee: James Reeves (james-reeves5546) => Nate Johnston (nate-johnston)

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

Title:
  Add a 'dscp' field to security group rules to screen ingress traffic
  by dscp tag as well as IP address

Status in neutron:
  Invalid

Bug description:
  This change will add to the current security group model an additional
  option to allow for traffic to be restricted to a given DSCP tag in
  addition to the current IP address based restriction.  Incoming
  traffic would need to match both the IP address/CIDR block as well as
  the DSCP tag - if one is set.

  Changes:
  * DB model changes to add a DSCP tag column to security groups.
  * API changes to allow for DSCP tag configuration options to be supplied to security group API calls.
  * Neutron agent changes to implement configuring IPTables with the additional DSCP tag configuration.

  Note: This is complimentary functionality to the "QoS DSCP marking
  rule support" change which, when implemented, will provide Neutron
  with an interface to configure QoS policies to mark outgoing traffic
  with DSCP tags.  See also: QoS DSCP marking rule support:
  https://bugs.launchpad.net/neutron/+bug/1468353

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