lar-e
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
lar-e [2015/07/09 04:27] Kevin Luehrs |
lar-e [2015/07/14 15:45] (current) Ashlee Young [Committers and Contributors:] |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== Project Name: Connectivity Services LSO ====== | ====== Project Name: Connectivity Services LSO ====== | ||
| * Proposed name for the project: Connectivity Services LSO | * Proposed name for the project: Connectivity Services LSO | ||
| - | * Proposed name for the repository: LSO-api | + | * Proposed name for the repository: lsoapi |
| * Project Categories: Requirements | * Project Categories: Requirements | ||
| Line 28: | Line 28: | ||
| * Reference: Metro Ethernet Forum Technical Specification MEF 7.2 Carrier Ethernet Management Information Model | * Reference: Metro Ethernet Forum Technical Specification MEF 7.2 Carrier Ethernet Management Information Model | ||
| - | The APIs and data models provide an interface for Ethernet services applications – including virtual network functions – to provision Ethernet services by configuring virtual or physical devices and the connections between them using OpenDaylight. | + | The APIs and data models provide an interface for Ethernet services applications – including virtual network functions – to provision Ethernet services by configuring virtual or physical devices and the connections between them using OpenDaylight. The RESTful interfaces exposed by the proposed APIs can be leveraged by other SDN controller platforms as well. |
| The Ethernet Services Manager, EVC Manager, CoS Manager and UNI Management plug-in are established as foundation services for future Ethernet services use cases. MEF defines a UNI as the physical demarcation point between the responsibility of the Service Provider and the responsibility of the Subscriber. The UNI terminates connections between customer locations and some characteristics of the Ethernet service such as line rate are enforced at the UNI. The UNI must therefore be deployed and configured to support the Ethernet service. | The Ethernet Services Manager, EVC Manager, CoS Manager and UNI Management plug-in are established as foundation services for future Ethernet services use cases. MEF defines a UNI as the physical demarcation point between the responsibility of the Service Provider and the responsibility of the Subscriber. The UNI terminates connections between customer locations and some characteristics of the Ethernet service such as line rate are enforced at the UNI. The UNI must therefore be deployed and configured to support the Ethernet service. | ||
| Line 38: | Line 38: | ||
| The proposed APIs are based on the capabilities of OpenDaylight to create and provision UNIs and EVCs on virtual or physical devices in the network. | The proposed APIs are based on the capabilities of OpenDaylight to create and provision UNIs and EVCs on virtual or physical devices in the network. | ||
| - | Proposed APIs follow the ETSI ISG NFV reference architecture, incorporating the UNI control and management planes into OpenDaylight and exposing MEF service definitions to the Virtualized Infrastructure Manager (VIM) through the Nf-Vi interface as indicated in Figure 2. | + | Proposed APIs follow the ETSI ISG NFV reference architecture, incorporating the UNI control and management planes into OpenDaylight and exposing MEF service definitions to OSS/BSS applications and to Virtual Network Functions as indicated in Figure 2. |
| The Ethernet Services Management API provides services to Ethernet Services applications so it may interface the applications in the OSS/BSS indirectly via the Os-Ma interface. | The Ethernet Services Management API provides services to Ethernet Services applications so it may interface the applications in the OSS/BSS indirectly via the Os-Ma interface. | ||
| Line 100: | Line 100: | ||
| * Committers | * Committers | ||
| * Kevin Luehrs, CableLabs K.Luehrs@cablelabs.com | * Kevin Luehrs, CableLabs K.Luehrs@cablelabs.com | ||
| - | * Adolfo Perez-Duran, CableLabs A.Perez-Duran@cablelabs.com | + | * Mufaddal Makati, CableLabs M.Makati@cablelabs.com |
| + | * Ashlee Young, Huawei ashlee@onosfw.com | ||
| * Contributors | * Contributors | ||
| * Kevin Luehrs, CableLabs | * Kevin Luehrs, CableLabs | ||
| - | * Adolfo Perez-Duran, CableLabs | ||
| * Mufaddal Makati, CableLabs M.Makati@cablelabs.com | * Mufaddal Makati, CableLabs M.Makati@cablelabs.com | ||
| + | * Prakash Ramchandran, Huawei Prakash.Ramchandran@huawei.com | ||
| * <TBD additional contributors> | * <TBD additional contributors> | ||
| Line 118: | Line 119: | ||
| ===== Proposed Release Schedule: ===== | ===== Proposed Release Schedule: ===== | ||
| - | The first release of the EPL service management API, UNI management API and data models is targeted for the second OPNFV release and ODL Beryllium. | + | The first release of the EPL service management API, UNI management API and data models is targeted for OPNFV Brahmaputra release and ODL Beryllium release. |
lar-e.1436416027.txt.gz · Last modified: 2015/07/09 04:27 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
