17:00:38 <KLuehrs> #startmeeting LSOAPI
17:00:38 <collabot> Meeting started Thu Nov  5 17:00:38 2015 UTC.  The chair is KLuehrs. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:38 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:00:38 <collabot> The meeting name has been set to 'lsoapi'
17:00:45 <KLuehrs> #chair KLuehrs
17:00:45 <collabot> Current chairs: KLuehrs
17:02:54 <KLuehrs> #topic Additional changes to OpenDaylight UNI Manager northbound interface
17:07:23 <KLuehrs> #info UNI Manager plug in northbound interface have changed: previous version of the UNI Mgr plug in were not part of the OpenDaylight topology model. This has  been changed, with an augmentation in UNI Mgr to work with ODL topology manager. This changed the northbound interface.
17:09:09 <KLuehrs> #info What does it mean for network elements to be 'aware' of OpenDaylight?
17:10:03 <KLuehrs> #info In the case of Open vSwitch, the instance can be configured to be 'passive' or 'active' mode. If in 'active' mode they know to register with OpenDaylight.
17:10:58 <KLuehrs> #info Does equipment need to have plug in software to know about OpenDaylight?
17:11:27 <KLuehrs> #info We don't know yet about NetConf or other protocols.
17:12:56 <KLuehrs> #topic MEF Resources Model update
17:37:14 <KLuehrs> #info Kevin shared work CableLabs is doing to develop a resource-level YANG model. The information will be contributed to MEF Network Resource Model project. Also the OpenDaylight UNI Manager project will use the Resource level YANG model to evolve the UNI Manager plug-in to OpenDaylight.
17:40:03 <KLuehrs> #info The resource level YANG model will include components and connections as defined by MEF resource layer model, e.g., UNI-N, INNI, Flow Domain, Flow Domain fragments. The change to the UNI Manager ODL plug in will enable applications to configure and activate the components and connections using OpenDaylight.
17:40:52 <KLuehrs> #info OpenDaylight allows network elements to register, which allows OpenDaylight to maintain a database of network elements in its domain.
17:43:10 <KLuehrs> #info What do network elements need to be able to register with OpenDaylight? Open vSwitch virtual switch software has 'passive' and 'active' modes. When in active mode OVS searches for a network controller to register with. No one attending the call today knew of other mechanisms for registering network elements with OpenDaylight. This is an area of further research for the UNI Manager
17:43:11 <KLuehrs> project.
17:43:21 <KLuehrs> #topic MEF LSO Hackathon
17:45:10 <KLuehrs> #info As mentioned in previous LSOAPI project meetings, the code developed in this project and OpenDaylight UNI Manager project is contributed to a hackathon being sponsored by MEF to advance its Lifecycle Service Orchestration (LSO) vision. The Hackathon will occur in conjunction with MEF GEN15 meeting in Dallas, TX November 16 - 18
17:45:16 <KLuehrs> #link https://wiki.mef.net/display/LH/MEF+LSO+Hackathon
17:47:46 <KLuehrs> #info Upcoming milestones for OPNFV Connectivity Services LSO project + OpenDaylight UNI Manager project: OPNFV Summit in San Francisco, CA November 9 - 12; MEF LSO Hackathon November 16 - 18; OPNFV Brahmaputra code release (code freeze Jan. 5, 2016); OpenDaylight Beryllium code release (code freeze Jan. 14, 2015)
17:48:27 <KLuehrs> #info NOTE: There will be no OPNFV LSOAPI project meeting next week, November 9 - 13 due to OPNFV Summit.
17:48:30 <KLuehrs> #endmeeting