lsoapi:documents:requirements
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
lsoapi:documents:requirements [2015/09/03 05:07] Kevin Luehrs [Information Model] |
lsoapi:documents:requirements [2015/11/29 21:21] (current) Kevin Luehrs [Connectivity Services LSO: Business Services CPE Virtualization] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | =====Connectivity Services LSO: Business Services CPE Virtualization===== | + | =====Connectivity Services LSO Requirements===== |
| - | Release 0.2.0 | + | Release 0.3.0 |
| - | September 3, 2015 | + | November 30, 2015 |
| Line 28: | Line 28: | ||
| - Ethernet Virtual Connection RESTful API | - Ethernet Virtual Connection RESTful API | ||
| - UNI Manager feature plug-in for OpenDaylight | - UNI Manager feature plug-in for OpenDaylight | ||
| + | |||
| + | The Connectivity Services LSO project will evolve the above-listed APIs and develop Ethernet Virtual Connection per User Network Interface (EVC per UNI) Manager API and Ethernet Virtual Connection Path Manager API. | ||
| ===History=== | ===History=== | ||
| Line 68: | Line 70: | ||
| ===E-LAN=== | ===E-LAN=== | ||
| - | E-LAN is multipoint-to-multipoint service, providing full mesh connectivity between UNI.== | + | E-LAN is multipoint-to-multipoint service, providing full mesh connectivity between UNI. |
| ===E-Access=== | ===E-Access=== | ||
| - | (Add description) | + | E-Access service type is defined by MEF as Ethernet services that use an Operator Virtual Connection (OVC) with at least one UNI OVC end point and one External Network-to-Network Interface (ENNI) OVC end point. This refers to the part of a multiple-service provider Ethernet service that is within a single provider's network. |
| ===Use Case for Initial Project Phase=== | ===Use Case for Initial Project Phase=== | ||
| Line 140: | Line 142: | ||
| Connectivity Services Manager API, Ethernet Virtual Connection Manager API, and Class of Service Manager API architecture is documented on the [[https://wiki.opnfv.org/lsoapi/documents/architecture|LSOAPI Architecture]] page. | Connectivity Services Manager API, Ethernet Virtual Connection Manager API, and Class of Service Manager API architecture is documented on the [[https://wiki.opnfv.org/lsoapi/documents/architecture|LSOAPI Architecture]] page. | ||
| - | Connectivity Services LSO APIs are designed following the information model. The APIs are documented using RESTful API Modeling Language (RAML). The RAML description of the APIs developed to date is posted on the [[https://wiki.opnfv.org/lsoapi/documents/apidocumentation|LSOAPI API Documentation]] page. HTML representation of the API documentation is available <page TBD>. | + | Connectivity Services LSO APIs are designed and implemented based on the information model. The APIs are documented using RESTful API Modeling Language (RAML). The RAML description of the APIs developed to date is posted on the [[https://wiki.opnfv.org/lsoapi/documents/apidocumentation|LSOAPI API Documentation]] page. HTML representation of the API documentation is available on the page <page TBD>. |
| Line 189: | Line 191: | ||
| * Integrate APIs and UNI Manager ODL feature plug-in for CRUD operations [Target date: December 18, 2015] \\ | * Integrate APIs and UNI Manager ODL feature plug-in for CRUD operations [Target date: December 18, 2015] \\ | ||
| - | - | + | Back to LSOAPI [[/lsoapi | main project page]] |
lsoapi/documents/requirements.1441256820.txt.gz ยท Last modified: 2015/09/03 05:07 by Kevin Luehrs
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
