Skip to content

Commit f2fa4b5

Browse files
committed
update background and postman files
1 parent 9164a7a commit f2fa4b5

File tree

5 files changed

+15
-6
lines changed

5 files changed

+15
-6
lines changed

‎README.md

+13-4
Original file line numberDiff line numberDiff line change
@@ -4,22 +4,31 @@
44

55
A team from Xoriant, Cisco, and Amartus has been working with Ethernet Virtual Connection (EVC) based Ethernet Services based on the Lifecycle Service Orchestration (LSO) architecture defined by MEF Forum (MEF). The implementation of these services has been done within the OpenDaylight UniMgr open source project. These EVC services are offered by service providers to their clients. There are six EVC services standardized by MEF, namely Ethernet Private Line (EPL), Ethernet Virtual Private Line (EVPL), Ethernet Private LAN (EP-LAN), Ethernet Virtual Private LAN (EVP-LAN), Ethernet Private Tree (EP-Tree), and Ethernet Virtual Private Tree (EVP-Tree).
66

7-
![E-Line service](./images/e-line.jpg)
7+
Here is a brief explanation of these services. Please also refer to [MEF 6.3] (https://www.mef.net/resources/mef-6-3-subscriber-ethernet-service-definitions/), [MEF 55.1] (https://www.mef.net/resources/mef-55-1-lifecycle-service-orchestration-lso-reference-architecture-and-framework/), and [MEF 10.4] (https://www.mef.net/resources/mef-10-4-subscriber-ethernet-services-attributes/) for additional information and the formal definition of each service.
88

99
An E-Line is a point-to-point Ethernet service that connects exactly two User Network Interface (UNI) end points. EPL and EVPL services both come under the E-Line service.
10+
11+
![E-Line service](./images/e-line.jpg)
12+
1013
An E-LAN is a multipoint-to-multipoint Ethernet service that connects at least two UNI endpoints, and possibly several UNI endpoints. Each UNI can communicate with any other UNI that is connected to that Ethernet service. EP-LAN and EVP-LAN services both come under the E-LAN service.
14+
15+
![E-LAN service](./images/e-lan.jpg)
16+
1117
An E-Tree is a rooted-multipoint ethernet service that connects at least two UNI end points, and possibly many UNI end points. The role of each UNI can be either root or leaf. A root UNI can communicate with all other root UNIs and all leaf UNIs, whereas a leaf UNI can communicate only with all root UNIs but not with any other leaf UNI. EP-Tree and EVP-Tree services both come under the E-Tree service.
12-
Please also refer to MEF 6.3, MEF 55.1, and MEF 10.4 for additional information and the formal definition of each service.
13-
18+
19+
![E-Tree service](./images/e-tree.jpg)
20+
1421
Ethernet Private services are port-based services, which means that only one such service can be provisioned on a given UNI. Ethernet Virtual Private services, on the other hand, are VLAN tag-based services, which means that multiple Ethernet Virtual Private services can be provisioned on one single UNI.
1522

1623
The UniMgr project implements these six services as a plugin for [OpenDaylight] (https://www.opendaylight.org/), an open source platform for customizing and automating networks of any size and scale. The services are implemented at the Legato and Presto layers as defined in Lifecycle Service Orchestration (LSO) architecture of MEF.
1724

25+
![LSO Architecture](./images/lso-architecture.png)
26+
1827
Legato is the topmost layer that interfaces with Operations Support Systems (OSS) / Business Support Systems (BSS), whereas Presto is an underlying layer that interacts with devices through respective drivers. The UniMgr project has provided support at Presto for several years. The team from Xorian recently contributed significant code to add support at Legato and provide important updates to Presto and the driver layer as well. This includes some validations at Legato that are over and above the validations specified in the corresponding YANG models. This ensures Legato receives absolutely valid requests and prevents rejection of equivalent API calls by the underlying Presto layer. The Presto layer has the ability to automatically determine an appropriate driver for various UNI hardware so that correct configurations are provisioned on all UNIs participating in the service. Full functionality of Create/Update/Delete/Inquire for all the six services is implemented as part of the UniMgr project. The code supports creating services on UNIs that are part of one device or that span multiple devices.
1928

2029
Currently, the UniMgr project supports devices compliant with Cisco XR (ASR 9000) devices. Cisco and Xorian collaborated to upgrade this support for work with more recently version of IOS XR software. The Xorian team can easily develop drivers for devices of other vendors to enable orchestration of these six services on other devices.
2130

22-
This repository provides a tutorial that can be used to try the UniMgr project for yourself. The tutorial demonstrates orchestration of these services using two Cisco XR devices running in a Cisco DevNet Sandbox. Postman scripts are used to invoke the Legato API with the necessary parameters to provision the services.
31+
This repository provides a tutorial that can be used to try the UniMgr project for yourself. The tutorial demonstrates orchestration of these services using two Cisco XR devices running in a Cisco DevNet Sandbox. Postman is used to invoke the Legato API with the necessary parameters to provision the services. This repo includes the Postman [environment](OpenDaylightXR Sandboxes.postman_environment.json) and [collection](./unimgr.postman_collection.json) referenced in the steps that follow.
2332

2433
## Create EVC Service using Cisco XR - Step By Step
2534

‎images/e-lan.jpg

67.6 KB
Loading

‎images/e-tree.jpg

63.6 KB
Loading

‎images/lso-architecture.png

67.3 KB
Loading

‎OpenDaylight XR Sandboxes.postman_environment.json renamed to ‎unimgr.postman_environment.json

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"id": "02b1bfdb-1d6b-4c82-aaf2-3239010410bb",
3-
"name": "OpenDaylight XR Sandboxes",
3+
"name": "unimgr-xr-sandbox",
44
"values": [
55
{
66
"key": "host",
@@ -129,6 +129,6 @@
129129
}
130130
],
131131
"_postman_variable_scope": "environment",
132-
"_postman_exported_at": "2021-08-27T19:16:54.690Z",
132+
"_postman_exported_at": "2021-09-07T20:55:40.074Z",
133133
"_postman_exported_using": "Postman/8.11.1"
134134
}

0 commit comments

Comments
 (0)