template design © 2007 supa – simplified use of policy abstractions policy-driven service...
TRANSCRIPT
TEMPLATE DESIGN © 2007
www.PosterPresentations.com
SUPA – Simplified Use of Policy Abstractions
Policy-driven Service Management
Date: Monday, March 23, 2015Time: 1300-1500 CDTRoom: GoldChairs: Dan Romascanu <[email protected]> Tina Tsou <[email protected]>Description:
The purpose of SUPA is to develop a methodology by which network services can be managed using standardized policyrules. SUPA will focus in the first phase on inter-datacenter
traffic management as part of the distributed data center usecase, including the automated provisioning of site-to-site
virtual private networks of various types.Mailing List Address: [email protected] Subscribe: https://www.ietf.org/mailman/listinfo/supa Archive: http://www.ietf.org/mail-archive/web/supa/ Jabber Chat Room Address: xmpp:[email protected]
Policy-driven Service Management
Network Manager (Controller)
Network Elements(routers, switches, etc)
RESTCONF / NETCONF
Service Manager
Network Elements(routers, switches, etc)
Service Data Model
Policy Data Model
Topology Data Model
Network Manager (Controller)
Topology Data Model
SUPA scope
Example of policy rules in the context of the SUPA use case
1. A user-defined policy received by Service Management (SM) is a high-level (abstracted) policy. For example, if a certain event occurs, some objects may require configuration changes.
For example, if bandwidth capacity in the link is larger than 80%, detour the traffic flow to a different link that has the required capacity:
name: traffic steering target: Data link L, VPN flow F, expr: flow f1: F | link capacity > threshold; action: enable detour;
2. The SM translates the high-level user-defined policy to a more concrete policy, and sends the more concrete policy to the controller.
a) The service data model describes a service. In this example, it contains basic information about nodes and connections among them in the DDC use case.
module: ietf-supa-ddc
+--rw ddc-service | +--rw ddc-service* [name] | +--rw name string | +--rw tenant-name string | +--rw dc-name*string | +--rw interface-name* string | +--rw connection-type? enumeration | +--rw connection-name string | +--rw vlanId? uint16 | +--rw bandwidth uint32 | +--rw latency uint32
b)The policy data model defines the events, conditions, and actions that make up the more concrete policy rule. This form of policy rule will be used to change the configuration of affected objects. In this example, it describes the pass/bypass action to specific nodes when the threshold is reached.
…(snipped) +--rw traffic-steering-policy +--rw bandwidth* [type] | +--rw type enumeration | +--rw value? uint32 +--rw threshold* [match] | +--rw match enumeration +--rw adjust-path +--rw constraint-nodes | +--rw constraint-node* [node-id] | +--rw node-id string | +--ro constraint-type? enumeration | +--rw sequence? uint32 …(snipped)
c)The more concrete policy is sent from the SM to the NM/C.
Action: IP traffic adjustment target: specific vpn-name; adjust-path to pass/bypass specific nodes;
3. The controller generates and issues device-specific policy rules (e.g., routing, resource adjustment) to affected network elements.
Relationship to other WGs
Network Manager
(Controller)
Network Elements(routers,
switches, etc)
RESTCONF / NETCONF
Service Manager
SUPA focuses on: service management and network resource view
Network Elements(routers,
switches, etc)
Other WGs (I2RS, IDR, PCE,
etc.) focus on: network element centric view
Network Manager
(Controller)