yahoo-eng-team team mailing list archive

[YujiAzama <azama-yuji@xxxxxxxxxxxxxxxxx>]

Public bug reported:

[Existing problem]
   This spec introduces a common classifier resource to Neutron API extension.
   This new resource can be leveraged to better realize other Neutron services
   needing traffic classification.

   Traffic classification is commonly needed by many Neutron services (e.g.
   Service Function Chaining [1]_, QoS [2]_, Tap as a Service [3]_, FWaaS [4]_,
   Group-Based Policy [5]_, and Forwarding Rule [6]_), but each service uses its
   own classifier resource similar to others. A common traffic classifier resource
   should exist in Neutron so that it could be leveraged across network services.

[What is the enhancement?]
   Add traffic classifiers to Neutron API as extension.

[Related information]
   Spec: https://review.openstack.org/#/c/190463/

[1] API for Service Chaining,
   https://review.openstack.org/#/c/192933/
[2] QoS,
   https://review.openstack.org/#/c/88599/ 
[3] Tap as a Service,
   https://review.openstack.org/#/c/96149/ 
[4] Firewall as a Service,
   http://specs.openstack.org/openstack/neutron-specs/specs/api/firewall_as_a_service__fwaas_.html
[5] Group-based Policy,
   https://review.openstack.org/#/c/168444/ 
[6] Forwarding Rule,
   https://review.openstack.org/#/c/186663/
[7] IANA Protocol Numbers,
   http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml

** Affects: neutron
     Importance: Undecided
     Assignee: YujiAzama (azama-yuji)
         Status: New


** Tags: rfe

** Description changed:

  [Existing problem]
-    This spec introduces a common classifier resource to Neutron API extension.
-    This new resource can be leveraged to better realize other Neutron services
-    needing traffic classification.
+    This spec introduces a common classifier resource to Neutron API extension.
+    This new resource can be leveraged to better realize other Neutron services
+    needing traffic classification.
  
-    Traffic classification is commonly needed by many Neutron services (e.g.
-    Service Function Chaining [1]_, QoS [2]_, Tap as a Service [3]_, FWaaS [4]_,	
-    Group-Based Policy [5]_, and Forwarding Rule [6]_), but each service uses its
-    own classifier resource similar to others. A common traffic classifier resource
-    should exist in Neutron so that it could be leveraged across network services.
+    Traffic classification is commonly needed by many Neutron services (e.g.
+    Service Function Chaining [1]_, QoS [2]_, Tap as a Service [3]_, FWaaS [4]_,
+    Group-Based Policy [5]_, and Forwarding Rule [6]_), but each service uses its
+    own classifier resource similar to others. A common traffic classifier resource
+    should exist in Neutron so that it could be leveraged across network services.
  
  [What is the enhancement?]
-    Add traffic classifiers to Neutron API as extension.
+    Add traffic classifiers to Neutron API as extension.
  
  [Related information]
-    Spec: https://review.openstack.org/#/c/190463/
+    Spec: https://review.openstack.org/#/c/190463/
+ 
+ [1] API for Service Chaining,
+    https://review.openstack.org/#/c/192933/
+ [2] QoS,
+    https://review.openstack.org/#/c/88599/ 
+ [3] Tap as a Service,
+    https://review.openstack.org/#/c/96149/ 
+ [4] Firewall as a Service,
+    http://specs.openstack.org/openstack/neutron-specs/specs/api/firewall_as_a_service__fwaas_.html
+ [5] Group-based Policy,
+    https://review.openstack.org/#/c/168444/ 
+ [6] Forwarding Rule,
+    https://review.openstack.org/#/c/186663/
+ [7] IANA Protocol Numbers,
+    http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml

** Changed in: neutron
     Assignee: (unassigned) => YujiAzama (azama-yuji)

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

Title:
  RFE - Add common classifier resource

Status in neutron:
  New

Bug description:
  [Existing problem]
     This spec introduces a common classifier resource to Neutron API extension.
     This new resource can be leveraged to better realize other Neutron services
     needing traffic classification.

     Traffic classification is commonly needed by many Neutron services (e.g.
     Service Function Chaining [1]_, QoS [2]_, Tap as a Service [3]_, FWaaS [4]_,
     Group-Based Policy [5]_, and Forwarding Rule [6]_), but each service uses its
     own classifier resource similar to others. A common traffic classifier resource
     should exist in Neutron so that it could be leveraged across network services.

  [What is the enhancement?]
     Add traffic classifiers to Neutron API as extension.

  [Related information]
     Spec: https://review.openstack.org/#/c/190463/

  [1] API for Service Chaining,
     https://review.openstack.org/#/c/192933/
  [2] QoS,
     https://review.openstack.org/#/c/88599/ 
  [3] Tap as a Service,
     https://review.openstack.org/#/c/96149/ 
  [4] Firewall as a Service,
     http://specs.openstack.org/openstack/neutron-specs/specs/api/firewall_as_a_service__fwaas_.html
  [5] Group-based Policy,
     https://review.openstack.org/#/c/168444/ 
  [6] Forwarding Rule,
     https://review.openstack.org/#/c/186663/
  [7] IANA Protocol Numbers,
     http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml

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