Upload
others
View
16
Download
0
Embed Size (px)
Citation preview
Multi-layer Multi-domain Network Topology Abstractions Using ONF
Transport APIKarthik Sethuraman, NEC
September 2019
*animated slides
ONF Transport API (TAPI): Functional Architecture
3
Topology Service
Connectivity Service
Path Computation Service
Shared Network Information Context
Virtual Network Service
Notification Service
NENetwork ElementsNENESDN Controller
NENESDN ControllerNENEApplication
Transport API or Other SBIs
Transport API or Other NBIs
OAM Service Equipment Inventory Service
Industry Adoption: Functional Interface solution that best fulfills conflicting requirements of stability (future proof, interoperability) & flexibility/agility (technology evolution)
OIF Transport API Interop Demo (2014, 2016, 2018)
4
Domain Controller
Domain Controller
Domain Controller
Multi-Domain Controller
Technology, Vendor Specificmodels
TAPI Agent
OSS/App/Orchestrator
Common Abstraction model
Transport API
Test Vendors
Test Carriers
Transport APITAPI Agent
Multi-Domain Controller
TAPI AgentTAPI Agent
TAPI AgentTransport API
MEF: Lifecycle Service Orchestration Reference Architecture (LSO RA)
5
MEF Common Resource Model
ONF TAPI Model
Simple Physical Network Example to illustrate T-API
PE3PE1
PE2
P4
CE4
CE3
CE5CE – Customer EdgePE – Provider EdgeP - Provider
CE1
CE2
CE6
UNI UNI
UNI
- A Network Provider (Blue) with two Customers (Red and Green)- All UNI interfaces are ETH (e.g. 10GE), I-NNI interfaces are OTU (e.g. 100G OTN)- All PE-NE are ODU/ETH switch capable, while P-NE is only ODU switch capable
Node Edge Point (Network Internal)
Node Edge Point (Network Edge)
Service Interface Point
Logical Termination Points
T-API Contexts for the Simple Network Example
Resource Group -PE1
Resource Group -PE2
Resource Group -PE3 Resource Group - P
Oth
er A
dmin
Int
erfa
ces
Provider Internal Context Resource Groups
Server ContextPE1
Server ContextPE2
Server ContextPE3
Server ContextP
Shared ContextRED
Resource Group
TAPI
Shared ContextGREEN
Resource Group
TAPI
Shared ContextPINK.Admin
Resource Group
TAPI
ApplicationRED SDN Controller GREEEN
Resource Group Resource Group
Admin APPPink
Client
Server
Client
Server
Provider SDN ControllerOrchestration / Virtualization
(based on ONF Architecture v1.1)
Example Topology Abstractions in the Shared Context
10
Mapping
G1
G2
G3
Green Shared Context
R1
Red Shared Context
P
PE1
PE2
PE3
Pink Admin Context
Node Edge Point (NW Internal)
Service Interface Point
Node Edge Point (NW Edge)
LinkTopology
NodeTransitional Link
Client-1 (Red) Shared Context: Single Node Topology
ETH
Connection
Connectivity Service
Shared Context
• Single Node abstraction example• Node and its NodeEdgePoints provide some approximation of the network capabilities• ConnectivityService can be requested between ServiceInterfacePoints• Connections appear as cross-connections across node, no visibility of underlying route
Node Edge Point (Internal)
Node Edge Point (Edge)
Service End Point
Link
Transitional Link
Mapping
Topology
Node
Connection EndPoint
Connection
Service Interface Point
Client 2 (Green) Shared Context: Multi-Node Topology
PE1 PE3
PE2ETH
Connection
Connectivity Service
Shared Context
• Multiple Nodes (PEs) Topology example• Node and its NodeEdgePoints provide reasonable information of their capabilities• ConnectivityService can be requested between ServiceInterfacePoints• Top-level Connection is recursively decomposed into lower-level Connections, 1 per Node • Connection route can be traced over the exposed Topology
Node Edge Point (Internal)
Node Edge Point (Edge)
Service End Point
Link
Transitional Link
Mapping
Topology
Node
Connection EndPoint
Connection
Service Interface Point
Admin (Pink) Shared Context: Multi-layer Topology
PE1o PE3o
P4o
PE2o
PE1e PE3e
PE2e
TAPI Context
Node Edge Point (Internal)
Node Edge Point (Edge)
Service End Point
Link
Transitional Link
Mapping
Topology
Node
Connection EndPoint
Connection
Service Interface Point
• Each physical device is represented by a separate Node per supported layer (ETH & ODU)• Node and its NodeEdgePoints provide information of their capabilities at that layer• Transitional Links interconnect the NodeEdgePoints at different layers• Top-level Connection is recursively decomposed into lower-level Connections, 1 per Node• Top-level Connections at lower (server) layer result in Links at upper (client) layer
1 2
3
1 2
3
N
Recursive Node & Topology aspects of Forwarding Domain
TAPI Context
01.1
01.n
02.1
02.n
Node aspect of FDTopology aspect of FDObserver
01
A FD (Node)Node Edge Point
Link
01.1 Service Interface Point
A FD (Topology)
Mapping
02`
01``
A
B04
C03`
01`
02
Context appears as a Topology N of one Node A and SIPs (off-network relationships/Links)
C.3C.4
C.1
C.2
11
14
16
1718
12
1315
03
01
Node-C appears a Topology of Nodes C.1-C.4 & Links between them
Node-A appears a Topology of Nodes B & C and Link B-C
C
N
Recursive Connectivity & Topology aspects of Forwarding
TAPI Context
01.1
01.n
02.1
02.n02`
01``
A
B04
C03`
01`
02
C.3C.4
C.1
C.2
11
14
16
1718
12
1315 03
01
Connection C appears as a route of Connections C.1,C.3,C.4 & in-between Links
Node aspect of FDTopology aspect of FDObserver
01
A FD (Node)Node Edge Point
Link
01.1 Service Interface Point
A FD (Topology)
Mapping
Connection Topology
Connection
Connection End Point
Connection A appears a route of Connections B,C and Link B-C
Top-level “Network” Connection A
C
TAPI Topology & Connectivity Instances Tree view (example1)
17
AN
C
AB
C1C
01
11
12
C316
17
C404
18
02
04
01`
03`
01``
02`
Topology
AN
C
AB
C1C
01
11
12
C3
1617
C404
18
02
04
01`
03`
01``
02`
Topology w/ Connectivity
A
C
B
C1
C3
C4
01
02
02
03
01
03
01
11
16
17
04
18
02
04
01
11
13
14
04
18
TopologyAAAA01
Node
Connection Topology
ConnectionNode Edge PointConnection End Point
Reference/PointerComposition
01` Node Edge Point Reference01 Connection End Point Ref
1515
TAPI 2.2 Example 1: Single-level Topology, Network-Node (Single) abstraction
ANode Topology
0201
0102
Node Edge Point
01
A NodeNode Edge PointReference (pointer)
LinkA Topology
01
Node Encapsulates Topology
01 Service Interfc Point
Connection End PointConnection End Point Reference (pointer)ConnectionConnectivity Service
• Single Node abstraction – for simple TAPI applications/clients that does not want to concern itself with Network topology & routing
• Ability to expose top-level “Network” Connection only – No way to represent top-level Connection’s route or its lower-level decomposed “cross” connections
TAPI Context
TAPI 2.2 Example 2a: Single-level Topology, Network abstraction w/ implicit Node
Network Topology
01
02
C.2.2
C.2.1
C.2.3
C.1.1
C.1.2
C.1.3
3433
31
12
11
13
102122
2625
2423
32
35
36
01
C.3 C.4 0408
0507
06 B 0203
Node Edge Point
01
A NodeNode Edge PointReference (pointer)
LinkA Topology
01
Node Encapsulates Topology
01 Service Interfc Point
Connection End PointConnection End Point Reference (pointer)ConnectionConnectivity Service
TAPI Context
• Implicit Top-level Singe Node (and its encapsulated Topology)• Provides ability to expose top-level “Network” Connection and its
Connection-topology/route as well as it decomposed lower-level “Cross” Connections
• Top-level Connection is NOT bounded by an explicit Node, while lower-level connections have a bounding Node
TAPI 2.2 Example 2b: Single-level Topology, Network abstraction /w multi-level implicit Nodes
Network Topology
0102
C.2.2
C.2.1
C.2.3
C.1.1
C.1.2
C.1.3
34
3331
12
11
13
102122
2625
2423
32
35
36
01
C.3 C.4 0408
0507
06B 0203
Node Edge Point
01
A NodeNode Edge PointReference (pointer)
LinkA Topology
01
Node Encapsulates Topology
01 Service Interfc Point
Connection End PointConnection End Point Reference (pointer)ConnectionConnectivity Service
TAPI Context
• A variation of example 2a – but with multiple levels of Implicit Nodes (and their encapsulated Topology hierarchy)
• Provides ability to expose top-level “Network” Connection and its Connection-topology/route as well as multiple levels of Connection decomposition
• Top-level Connection as well as intermediate-level connections are NOT bounded by an explicit Node, while lowest-level connections have a bounding Node
TAPI 2.2 Example 3: 2-level Topology, Network abstraction w/ Explicit Node
Network Topology
C.2.2
C.2.1
C.2.3
C.1.1
C.1.2
C.1.3
3433
31
12
11
13
102122
2625
2423
32
35
36
01
C.3 C.4 0408
0507
06 B 0203
ANode Topology
0102
Node Edge Point
01
A NodeNode Edge PointReference (pointer)
LinkA Topology
01
Node Encapsulates Topology
01 Service Interfc Point
Connection End PointConnection End Point Reference (pointer)ConnectionConnectivity Service
01 02
TAPI Context
• This abstraction emerges from example 2a, with distinction of an Explicitbounding Node for “Network” Connection which allows for clean representation of forwarding capability prior to setting up of connectivity
• Provides ability to expose top-level “Network” Connection and its Connection-topology/route as well as its decomposed lower-level “Cross” Connections
• All Connections are bounded by an explicit Node
TAPI 2.2 Example 4: Multi-level Topology Partitioning abstraction
A
C B
C.2
C.1C.3
C.4
Node Topology
Topology A
Topology C
C.2.2
C.2.1
C.2.3
Topology C.2
C.1.1
C.1.2
C.1.3
Topology C.1
01 02
01 0204
3433
31
04
03
12
0805
0706
1112
13
10
11
13
102122
2625
2423
32
35
36
01
01
Node aggregates NEPs exposed by
Encapsulated Topology
TAPI Context
01 02
Node Edge Point
01
A NodeNode Edge PointReference (pointer)
LinkA Topology
01
Node Encapsulates Topology
01 Service Interfc Point
Connection End PointConnection End Point Reference (pointer)ConnectionConnectivity Service
• Emerges from example 2b - with distinction of multiple levels of Explicit Nodes (and their encapsulated Topology hierarchy)
• Provides ability to expose multi-level Connections, each bounded by an explicit Node
TAPI 2.2 v/s RFC8345 Topology Models: Simplified View
23
TopologyContext
TapiContext(ROOT)
Topology
Node
NodeEdgePoint
Link
Networks (ROOT)
Network
Node
TerminationPoint
Link
Augment
Tapi 2.2 Topology (Partitioning & Layering) RFC 8345 Topology (View mapping)
2..*
Composition (YANG list)Shared (YANG leafref + require_instance=true)
Association (YANG leafref + require_instance=false)
Augment (YANG augment + uses + container)
Augment (YANG augment + uses)
* all TAPI & RFC 8345 associations not shown
0..*
0..1
0..*
PoolsNEPsInSameNode
AggregatesNEPsExposedBy
UnderlyingTopology
Encapsulates Topology
Terminates On
SupportedBy
SupportedBy
SupportedBy
SupportedBy
Source
Destination
TAPI 3.0 augments RFC8345 Topology Model (under discussion)
24
TopologyContext
Topology
Node
NodeEdgePoint
Link
Networks (ROOT)
Network
Node
TerminationPoint
Link
Tapi 2.2 Topology (Partitioning & Layering) RFC 8345 Topology (View mapping)
2..*
Composition (YANG list)Shared (YANG leafref + require_instance=true)
Association (YANG leafref + require_instance=false)
Augment (YANG augment + uses + container)
Augment (YANG augment + uses)
* all TAPI & RFC 8345 associations not shown
0..*
0..1
0..*
PoolsNEPsInSameNode
AggregatesNEPsExposedBy
UnderlyingTopology
Encapsulates Topology
Terminates On
SupportedBy
SupportedBy
SupportedBy
SupportedBy
Source
Destination
Augment
Augment
Augment
Augment
TAPI 3.0 Example 5: Multi-level Topology Partitioning via Mapping abstraction
A
C B
C.2
C.1C.3
C.4
Node Topology
Topology A
Topology C
C.2.2
C.2.1
C.2.3
Topology C.2
C.1.1
C.1.2
C.1.3
Topology C.1
02
3433
31
04
03
12
0805
0706
11
13
102122
2625
2423
32
35
36
01
TAPI Context
01 02
Node Edge Point
01
A NodeNode Edge PointReference (pointer)
LinkA Topology
01
Node Encapsulates Topology
01 Service Interfc Point
Connection End PointConnection End Point Reference (pointer)ConnectionConnectivity Service
• Emerges from example 4 - with distinction of multiple clones NEPs & CEPs at every hierarchy level
01``
02`
04`
01`
11`12`
13`
10`
01```
NEP Supported By NEP
TAPI 3.0 Example 6: Multiple Topology Views via Mapping abstraction
Network Topology
N.4
N.3
N.5
N.1
N.2
N.6
3433
31
12
11
13
102122
2625
2423
32
35
36
01
N.7 N.8 0408
0507
06 N.9 0203
Node Edge Point
01
A NodeNode Edge PointReference (pointer)
LinkA Topology
01
Node Encapsulates Topology
01 Service Interfc Point
Connection End PointConnection End Point Reference (pointer)ConnectionConnectivity Service
TAPI Context
NEP Supported By NEP
ANode Topology
02`01``
X.2
X.1
X.3 X.4Topology C
02`0`8 05`
07`06`
01`
11`
12`13`
10`
Y.1 Y.2Topology B
02`05`01` 06`
• Provides ability to provide & map different intermediate views of an single underlying Topology
01 02
ONF ODTN (Open Disaggregated Transport) Architecture
27
OLS Controller
WSS TRN
Open Line System (OLS)
OpenConfig OpenConfig
MUX WSSAMP MUXTRN
ONOS
With OLS Controller
TAPI
Has topology
TAPI
RDM2
RDM1
RDM4RDM3 RDM5OLS Domain
I-NNI2
I-NNI1
I-NNI3
Operator Domain Topology – Partitioning to abstract layer network
28
Orchestration view
ONOS Controller View
OLS Controller View
UNI
TPD3
TPD1TPD2 E-NNIOLS Node
ONOS-OLS TAPI Context
Orchestrator-ONOS TAPI Context (LSO Presto)
Node Edge Point (Network Internal)Node Edge Point (Network Edge)Service Interface Point
Logical Termination Points shown
Connectivity Service End Point
Connection / Connection End PointPhotonic ConnectionPhotonic Media Channel
AbbreviationsTPD – Transponder NodeRDM – ROADM NodeUNI – User-Network InterfaceNNI – Network-Network InterfaceDSR – Digital Signal RateOTSi – Optical Tributary SignalOTSiA – OTSi AssemblyMC – Media Channel
100G
100G
100G
100G
100G
100G
100G
100G
RDM2
RDM1
RDM4RDM3 RDM5OLS Domain
I-NNI2
I-NNI1
I-NNI3
Operator Domain Connectivity Service & Resources
29
Photonic Connectivity Service 1
Photonic Connectivity Service 2
UNI
TPD3
TPD1TPD2 E-NNIOLS Node
OTSi 1-1
OTSi 1-1OTSi 1-2
OTSi 1-2
OTSi 2-1
OTSi 2-1
OTSi 2-2OTSi 2-2
OTSiA1 200GDSR1 100G
DSR3 100GOTSiA2 200G
OTSi-MC1
OTSi-MC3
OTSi-MC2
OTSi-MC4
OTSi-MC1
OTSi-MC3
OTSi-MC2
OTSi-MC4
ONOS-OLS TAPI Context
Orchestrator-ONOS TAPI Context (LSO Presto)
Node Edge Point (Network Internal)Node Edge Point (Network Edge)Service Interface Point
Logical Termination Points shown
Connectivity Service End Point
Connection / Connection End PointPhotonic ConnectionPhotonic Media Channel
DSR2 100G
AbbreviationsTPD – Transponder NodeRDM – ROADM NodeUNI – User-Network InterfaceNNI – Network-Network InterfaceDSR – Digital Signal RateOTSi – Optical Tributary SignalOTSiA – OTSi AssemblyMC – Media Channel
100G
100G
100G
100G
100G
100G
100G
DSR Connectivity Service 1 (100G)
DSR Connectivity Service 3 (100G)
DSR Connectivity Service 2 (100G)
100G
Thank You
Follow Up Links:https://wiki.opennetworking.org/display/OTCC/TAPI