lsoapi
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
lsoapi [2016/02/01 17:28] Kevin Luehrs [Project Description:] |
lsoapi [2016/02/16 20:16] Kevin Luehrs [Project: Connectivity Services LSO] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Project: Connectivity Services LSO ===== | ===== Project: Connectivity Services LSO ===== | ||
| + | |||
| + | ===February 16, 2016=== | ||
| + | OPNFV TSC approved terminating Connectivity Services LSO project: \\ | ||
| + | http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-02-16-14.59.html | ||
| + | |||
| + | ---- | ||
| =====Project Termination Request===== | =====Project Termination Request===== | ||
| Line 12: | Line 18: | ||
| (3) In the ODL UNI Manager project current plans are to evolve the plug-in to incorporate Service Layer YANG model and Resource Layer YANG model. This will supersede and obsolete the 'basic' Service Layer functionality currently being provided by LSOAPI. That is, if the current plan for UNI Manager comes to fruition, LSOAPI will not be needed to provide Service Layer functionality as it will be replaced with more complete Service Layer functionality in OpenDaylight. \\ | (3) In the ODL UNI Manager project current plans are to evolve the plug-in to incorporate Service Layer YANG model and Resource Layer YANG model. This will supersede and obsolete the 'basic' Service Layer functionality currently being provided by LSOAPI. That is, if the current plan for UNI Manager comes to fruition, LSOAPI will not be needed to provide Service Layer functionality as it will be replaced with more complete Service Layer functionality in OpenDaylight. \\ | ||
| (4) OPNFV requirements for projects to be included in the Brahmaputra release include executing project code on an instance of OPNFV Pharos release and include LSOAPI testing in Brahmaputra continuous integration environment. This presents a challenge that has so far proven intractable to the LSOAPI project due to lack of access to appropriate Pharos resource and to lack of appropriate resource familiar with Brahmaputra CI environment. \\ | (4) OPNFV requirements for projects to be included in the Brahmaputra release include executing project code on an instance of OPNFV Pharos release and include LSOAPI testing in Brahmaputra continuous integration environment. This presents a challenge that has so far proven intractable to the LSOAPI project due to lack of access to appropriate Pharos resource and to lack of appropriate resource familiar with Brahmaputra CI environment. \\ | ||
| + | |||
| + | Note: The requirement for Service Layer functionality that LSOAPI provides for the initial proof-of-concept for configuration of Carrier Ethernet services using open source controller platform does not go away. Our vision is it will migrate to a more full-featured implementation in OpenDaylight. So while the LSOAPI project is terminated the function it was initially created to provide could be implemented in OpenDaylight and incorporated in OPNFV indirectly, as part of OpenDaylight. | ||
| __Estimated Impact on Other OPNFV Projects__ \\ | __Estimated Impact on Other OPNFV Projects__ \\ | ||
lsoapi.txt ยท Last modified: 2016/02/16 20:16 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
