Bug 1042614 - [RFE][neutron]: Integrated APIs for specification of connectivity (L2 and L3) as well as network services (FW, LB, NAT, QoS... )
Summary: [RFE][neutron]: Integrated APIs for specification of connectivity (L2 and L3)...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/neut...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 00:30 UTC by RHOS Integration
Modified: 2015-11-20 19:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 16:56:21 UTC
Target Upstream Version:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.