4.2 Inter-Op Progress and Considerations in Abstraction

Download Report

Transcript 4.2 Inter-Op Progress and Considerations in Abstraction

Multi-layer Multi-domain Inter-op Test
based on ACTN Architecture
SDN RG, IETF 97th, Seoul, Korea
Haomian Zheng ([email protected])
Young Lee([email protected])
Daniele Ceccarelli ([email protected])
Jong Yoon Shin ([email protected])
Yunbin Xu([email protected])
Yunbo Li([email protected])
Yan Shi([email protected])
Boyuan Yan([email protected])
ACTN Goal
• Abstraction and Control of Traffic-Engineering Networks
– Considered as “SDN Architecture & Solution” in IETF
– Compatible in supporting legacy heterogeneous transport network
control/management technologies (e.g., GMPLS/ASON, PCE,
NMS/EMS).
• SDN controllers’ hierarchy and roles
– Customer network controllers (CNC)
– Multi-domain service coordinators (MDSC)
– Physical network controllers (PNC)
• Multi-domain service coordination based on abstraction/virtualization.
– Distributed data centers dispersed over different domains including
wireless backhaul transport, metro and core packet/optical
networks.
ACTN Architecture:
CNC
MDSC
MDSC
CNC
CNC
Customer
Network
Controller
CMI
Allow Recursion
Multi-domain
Service
MDSC
Coordinator
Coordination Layer
MPI
MDSC
PNC
(Access)
Customer Layer
PNC
PNC (IP)
(Transport)
PNC
(Transport)
PNC (IP)
Physical
Network Network Control Layer
Controller
SBI
Physical Layer
Inter-op introduction
MDSC
MPI
Choice 1: RESTConf+YANG
Choice 2: PCEP
PNC
PNC
PNC
PNC
IP/MPLS
Transport
Transport
IP/MPLS
• Based on Emulators;
• Inter-op focused on ACTN MPI:
– Operators are welcomed to discuss or develop their own MDSC;
– Vendors are expected to have PNC and device emulators with
corresponding solution on Southbound Interface
• Multi-layer, multi-domain and multi-protocol is supported;
Related IETF work
• ACTN:
– draft-ietf-teas-actn-requirements
– draft-ietf-teas-actn-framework
• Applicability:
– draft-zhang-teas-actn-yang
– draft-dhody-pce-applicability-actn
• Yang model (with RESTconf)
– For Topology: Based on draft-ietf-teas-yang-te-topo-04
– For Services: Based on draft-zhang-teas-transport-servicemodel-00
• PCEP:
– For Topology: draft-dhodylee-pce-pcep-ls-04
– For Services: draft-ietf-pce-pce-initiated-lsp-05/draftdhodylee-pce-stateful-hpce
ACTN Test Case (1) – Topology Abstraction
MDSC
MPI
PNC (IP)
PNC (T)
PNC (IP)
Topology Abstraction Steps:
•
•
Preparation (respective TED & Abstraction Algorithm as per PNC):
Each PNC report abstracted topology to MDSC; MDSC create its TED;
• RESTconf: Get message with topo model for initial topo, with notification on changes;
• PCEP-LS: LSRpt message for both initial topology and changes;
• MDSC need to detect the cross-domain link, and stitching to get full topology;
ACTN Test Case(2) – E2E Service Provision
•
Service Provisioning Steps:
• MDSC initiate a service provisioning request;
• RESTconf: POST message with Service YANG model;
• Use Hierarchical PCInitiate for PCEP;
• Each PNC compute intra-domain path, and establish it respectively;
• Process is domain-specific, report to MDSC via standard HTTP message;
• MDSC should have DELETE operation;
ACTN Test Case(3) – Bandwidth Adjustment
Service A
DC1
A1
A2
B1
B2
C1
C2
A3
A4
B3
B4
C3
C4
DC2
Service B
• Bandwidth adjustment Steps:
• Set up two ‘existing’ LSPs, say 30G and 10G respectively;
• Update the bandwidth for two LSPs:
– RESTconf: PUT message with Service model;
– PCEP: PCUpd and PCRpt message;
• Looks like a ‘DC load balance’;
DC3
ACTN Test Case(4) – Inter-domain Restoration
MDSC
MPI
PNC (IP)
PNC (T)
PNC (IP)
DC2
DC1
DC3
• Inter-domain Restoration Steps
• Create one service between DC1 and DC2;
• Detect a ‘failure’ in transport domain, and assume there is not enough
resources to do intra-domain restoration; need to report to MDSC;
• MDSC create backup inter-layer paths based on failure notification;
Future work
• Future Work:
– Continue our job on inter-op test;
– Result will be published in ACTN wiki after IETF:
https://sites.google.com/site/openactn/interoperability
-demo/multi-vendor-inter-op-test ;
– We are willing to see interests and partners to work
together.
• Suggest to IETF&SDN RG:
– Would be nice to see official inter-op test events
THANK YOU!
BNB DEMO AVAILABLE ON THURSDAY NIGHT!