16:01:30 <KLuehrs> #startmeeting LSOAPI
16:01:30 <collabot> Meeting started Thu Sep  3 16:01:30 2015 UTC.  The chair is KLuehrs. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:30 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:01:30 <collabot> The meeting name has been set to 'lsoapi'
16:01:45 <KLuehrs> #chair KLuehrs
16:01:45 <collabot> Current chairs: KLuehrs
16:02:33 <KLuehrs> #topic Connectivity Services LSO Requirements
16:23:16 <KLuehrs> #info CableLabs call for action: request additional developer participation for API development as listed in the Implementation Plan section of the LSOAPI Requirements
16:23:44 <KLuehrs> #topic Connectivity Services Manager API and EVC Manager API updates
16:24:10 <KLuehrs> #info Brian O provided an update on the status of the APIs and called for developer participation
16:26:45 <KLuehrs> #info Steve S shared LSOAPI documentation in HTML format. This will be posted for public access within a week's time.
16:27:51 <KLuehrs> #info LSOAPI project APIs were documented using RESTful API Modeling Language (RAML)
16:31:43 <KLuehrs> #topic OpenDaylight UNI Manager Plug-in - to - Network Element Architecture
16:33:30 <KLuehrs> #info 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).
16:34:53 <KLuehrs> #info 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.
16:38:55 <KLuehrs> #info Open question: should LSOAPI project standardize the REST interface to external devices?
16:39:44 <KLuehrs> #info Question: Should we use API interface provided by OpenDaylight and rely upon equipment vendors to interface to that?
16:41:45 <KLuehrs> #info Standardizing UNI Manager OpenDaylight northbound API interface is
16:45:13 <KLuehrs> #info OpenDaylight SDN controller vendors need to solve the problem of interfacing with networking equipment.
16:45:33 <KLuehrs> #topic LSOAPI Information Model: EVC per UNI Class
16:46:16 <KLuehrs> #info Steve S shared the initial LSOAPI information model (UML), focusing on the EVC per UNI attributes
16:47:52 <KLuehrs> #info 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.
16:51:36 <KLuehrs> #info Many of the individual EVC per UNI attributes requires knowledge of MEF specifications and Ethernet
16:54:53 <KLuehrs> #info 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.
16:55:18 <KLuehrs> #topic Metro Ethernet Forum LSO Hackathon
16:59:57 <KLuehrs> #info 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.
17:00:33 <KLuehrs> #endmeeting