#opnfv-meeting: LSOAPI

Meeting started by KLuehrs at 16:00:20 UTC (full logs).

Meeting summary

  1. Changes to OpenDaylight UNI Manager northbound interface and impacts to Connectivity Services LSO APIs (KLuehrs, 16:05:03)
    1. The UNI Manager plug-in for OpenDaylight, which is closely related to Connectivity Services LSO (LSOAPI), has been updated. The updates to UNI Manager changed the northbound REST interface that LSOAPI uses. (KLuehrs, 16:08:22)
    2. Brian Otte is investigating the changes to the UNI Mgr northbound APIs but investigation is impeded by the latest versio n of UNI Mgr from the OpenDaylight UNI Mgr repository not building correctly. (KLuehrs, 16:09:47)
    3. UNI Mgr code includes documentation of all possible REST calls but LSOAPI is not using all of them. (KLuehrs, 16:10:50)
    4. Browser developer interface showed call to ODL operational data store was failing (KLuehrs, 16:12:43)
    5. Correction, ODL build worked but when Karaf was launched errors were reported. Changes were made and committed early today to UNI Mgr but Brian has not had an opportunity to try re-building Karaf yet today. (KLuehrs, 16:14:44)
    6. Brian made changes to a local copy of LSOAPI code to match the changes to UNI Mgr northbound REST interface. Assuming the error has been corrected and karaf launches correctly, he will try later today to exercise the LSOAPI code with the updated UNI Mgr plug in. (KLuehrs, 16:16:57)
    7. Brian observed that there is a pending change to UNI Mgr in UNI Mgr Gerrit to integrate with ODL Topology Manager. (KLuehrs, 16:20:02)
    8. Note: The change to UNI Mgr to integrate with ODL topology manager will change the URL to identify where in the network the UNI is. (KLuehrs, 16:22:03)
    9. ODL topology manager can represent network elements as nodes or as links. In the case of UNI Mgr use case ODL can potentially show UNIs and the links between them. (KLuehrs, 16:23:09)
    10. We should know more today about whether LSOAPI and UNI Manager current functionality (KLuehrs, 16:41:24)

  2. Updates to MEF Resources model and impacts to Connectivity Services LSO APIs (KLuehrs, 16:42:21)
    1. MEF recently created Resource Model project to define resource-layer components and attributes for delivery of Carrier Ethernet services. (KLuehrs, 16:43:13)
    2. UNI Manager plug-in to OpenDaylight will need to evolve to comply with the new Resource Model specification. (KLuehrs, 16:43:55)
    3. LSOAPI will in turn need to evolve to interface to the new UNI Manager plug-in interface (KLuehrs, 16:44:19)
    4. This work has begun for UNI Manager: CableLabs has begun developing a draft resource layer information model that will be contributed to the MEF Resource Model project. MEF RM project forecasts a published specification in 2Q 2016. (KLuehrs, 16:47:27)

  3. MEF LSO Hackathon (KLuehrs, 16:47:55)
    1. MEF is hosting an LSO Hackthon in Dallas, TX November 14 - 16 to progress their vision of MEF Lifecycle Services Orchestration. LSOAPI code and UNI Manager code is being contributed to the Hackathon as base code for developers to evolve. (KLuehrs, 16:49:39)
    2. https://wiki.mef.net/display/LH/MEF+LSO+Hackathon (KLuehrs, 16:50:05)
    3. CableLabs attendees discussed possibilities for harmonizing the two code sets (LSOAPI + UNI Manager and code submitted by MEF Service Configuration and Activation project). More discussion will follow offline. (KLuehrs, 17:03:21)


Meeting ended at 17:03:24 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. KLuehrs (24)
  2. collabot (7)
  3. Luehrs (0)
  4. Kevin (0)


Generated by MeetBot 0.1.4.