Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
SUPA – Simplified Use of Policy Abstractions Policy-driven Service Management Date: Monday, March 23, 2015 Time: 1300-1500 CDT Room: Gold Chairs: Dan Romascanu <[email protected]>, Tina Tsou <[email protected]> Description: The purpose of the SUPA is to develop a methodology by which management of network services can be done using standardized policy rules. SUPA will focus in the first phase on inter-datacenter traffic management in the use case of a distributed data center, including the automated provisioning of site-to-site virtual private networks of various types. Mailing List Address: [email protected] To Subscribe: https://www.ietf.org/mailman/listinfo/supa Archive: http://www.ietf.org/mail-archive/web/supa/ Jabber Chat Room Address: xmpp:[email protected] An example of standardized policy rules , potentially in the context of supa use case (a) name: traffic steering target: Data link L, VPN flow F, expr: flow f1: F | link capacity >= threshold; action: enable detour; 1 Service Manager Service Data Model (b) +--rw createDdcServices | +--rw ddcService* [tenantName] | +--rw tenantName string | +--rw dcName* string | +--rw tenantNetworkId* string | +--rw connectionType? enumeration +--rw createVpnInstancesforDdc | +--rw vpnInstance* [vpnName] | +--rw vpnName string | +--rw vlanId? uint16 | +--rw dataCenterInformation* [dcName] | | +--rw dcName string | | +--rw interfaceName? string | +--rw vpnType? enumeration | +--rw bandWidth? uint32 | +--rw latency? uint32 … Policy Data Model 2 RESTCONF / NETCONF … +--rw TrafficSteeringPolicy +--rw bandwidth +--rw Type enumeration +--rw value uint32 +--rw threshold string +--rw match enumeration +--rw action +--rw pass string +--rw bypass string (c) +--NodeList string +--SiteList string (d) Network Manager (Controller) Network Manager (Controller) Topology Data Model Topology Data Model Policy: IP traffic adjustment target: specific vpnname; pass/bypass specific nodelist; 3 Network Elements Network Elements (routers, switches, etc) (routers, switches, etc) Policy-driven Service Management : SUPA scope Service Manager Service Data Model Policy Data Model RESTCONF / NETCONF Network Manager (Controller) Network Manager (Controller) Topology Data Model Topology Data Model Network Elements Network Elements (routers, switches, etc) (routers, switches, etc) 1. The user defined policy received by Service Management, is a high-level (abstracted) one: in the case of a certain event occurs, the adjustment on some objects is needed. E.g., if bandwidth capacity in the link is larger than 80%, detour the traffic flow to other link, like (a) in the figure. 2. Based on the service data model and policy data model, SM issues a middle-level(less abstracted) policy to controller after analyzing and processing according to policy from user. 1)The service data model describes the service, in this example it contains the basic information about node and connection among them in DDC use case, as shown by (b) in the figure. 2)The policy data model describes the event, constrain and actions for adjustment purpose, as shown by (c) in the figure. In this example, it describes the pass/bypass action to specific nodes when the threshold is reached. 3)The middle-level(less abstracted) policy, generated based on the highlevel user defined policy received and the two models aforementioned, is sent from SM to NM/C as shown by (d) in the figure. 3. Controller generates and issues specific policy (routing, resource adjustment, etc) to NE according to what it received from SM and the topology data model. TEMPLATE DESIGN © 2007 www.PosterPresentations.com