#opnfv-meeting: LSOAPI

Meeting started by KLuehrs at 16:01:30 UTC (full logs).

Meeting summary

  1. Connectivity Services LSO Requirements (KLuehrs, 16:02:33)
    1. CableLabs call for action: request additional developer participation for API development as listed in the Implementation Plan section of the LSOAPI Requirements (KLuehrs, 16:23:16)

  2. Connectivity Services Manager API and EVC Manager API updates (KLuehrs, 16:23:44)
    1. Brian O provided an update on the status of the APIs and called for developer participation (KLuehrs, 16:24:10)
    2. Steve S shared LSOAPI documentation in HTML format. This will be posted for public access within a week's time. (KLuehrs, 16:26:45)
    3. LSOAPI project APIs were documented using RESTful API Modeling Language (RAML) (KLuehrs, 16:27:51)

  3. OpenDaylight UNI Manager Plug-in - to - Network Element Architecture (KLuehrs, 16:31:43)
    1. Steve S presented a view/architecture of the interaction between the APIs and the OpenDaylight UNI Manager plug-in, and between the OpenDaylight UNI Manager plug-in and network elements (physical and virtual devices). (KLuehrs, 16:33:30)
    2. MEF specifications currently do not address how to provision specific network elements. The LSOAPI project is necessarily addressing this while trying to remain consistent with MEF services definitions and OpenDaylight architecture. (KLuehrs, 16:34:53)
    3. Open question: should LSOAPI project standardize the REST interface to external devices? (KLuehrs, 16:38:55)
    4. Question: Should we use API interface provided by OpenDaylight and rely upon equipment vendors to interface to that? (KLuehrs, 16:39:44)
    5. Standardizing UNI Manager OpenDaylight northbound API interface is (KLuehrs, 16:41:45)
    6. OpenDaylight SDN controller vendors need to solve the problem of interfacing with networking equipment. (KLuehrs, 16:45:13)

  4. LSOAPI Information Model: EVC per UNI Class (KLuehrs, 16:45:33)
    1. Steve S shared the initial LSOAPI information model (UML), focusing on the EVC per UNI attributes (KLuehrs, 16:46:16)
    2. MEF 6.2 specification describes EVC per UNI attributes. The EVC per UNI attribute descriptions in the MEF specifications get complicated and the LSOAPI information model needs to be updated to more accurately represent EVC per UNI attributes. (KLuehrs, 16:47:52)
    3. Many of the individual EVC per UNI attributes requires knowledge of MEF specifications and Ethernet (KLuehrs, 16:51:36)
    4. Lance H: How do we plan to address EVC per UNI attributes and how we model them in the project? We will have to organize the information internally so we can present options, and this will be a topic for future meetings. (KLuehrs, 16:54:53)

  5. Metro Ethernet Forum LSO Hackathon (KLuehrs, 16:55:18)
    1. Metro Ethernet Forum posted a public web page about the Hackathon (linked in LSOAPI Sept. 3 meeting agenda). The project labeled 'UNI Manager Project' on the Hackathon diagram on the page is the LSOAPI project. Hackathon is scheduled for November 16 - 18, 2015. Registration link is on the MEF Hackathon web page. Only 50 participants will be allowed to register. (KLuehrs, 16:59:57)


Meeting ended at 17:00:33 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. KLuehrs (23)
  2. collabot (4)


Generated by MeetBot 0.1.4.