Bug 1042614

Summary: [RFE][neutron]: Integrated APIs for specification of connectivity (L2 and L3) as well as network services (FW, LB, NAT, QoS... )
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/quantum-integrated-l2-l3-services-api
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:56:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-13 00:30:45 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/quantum-integrated-l2-l3-services-api.

Description:

Integrated APIs for specification of connectivity services (L2 and L3) as well as network services (FW, LB, NAT, QoS, ...). Abstractions used are:

- Port/EndPoint – an abstraction for tenant or provider end point that participates in NaaS (Port in API v2)

- Groups - aggregation of EndPoints used for managing them as a single entity ( there is no equivalent resource in API v2). “Managing” here is means: providing a connectivity service (L2, L3) to a group and applying a one or more Policies (security, qos, load balancing, NAT, …) which defines desired network service to be provided to a group

- Network/L2Domain – has the same semantics as Network in API v2

- L3Domain – provides L3 connectivity to L2Domains which are underlying it

- Policy is an abstraction for a collection of Rules that jointly define/affect  the expected behavior of the object it is applied to. Examples are SecurityPolicy (which is similar to the concept of SecurityGroup), LoadBalancingPolicy, etc ...

- Rule - is contained in the policy and its specification follows “condition followed by an action” pattern. Condition usually implies some sort of traffic matching expression expressed as triplet consisting of parameter, followed by an operator, followed by a value.


Specification URL (additional information):

None