======================
#opnfv-meeting: LSOAPI
======================


Meeting started by KLuehrs at 17:00:38 UTC.  The full logs are available
at
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-11-05-17.00.log.html
.



Meeting summary
---------------

* Additional changes to OpenDaylight UNI Manager northbound interface
  (KLuehrs, 17:02:54)
  * 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.  (KLuehrs, 17:07:23)
  * What does it mean for network elements to be 'aware' of
    OpenDaylight?  (KLuehrs, 17:09:09)
  * 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.  (KLuehrs, 17:10:03)
  * Does equipment need to have plug in software to know about
    OpenDaylight?  (KLuehrs, 17:10:58)
  * We don't know yet about NetConf or other protocols.  (KLuehrs,
    17:11:27)

* MEF Resources Model update  (KLuehrs, 17:12:56)
  * 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.  (KLuehrs, 17:37:14)
  * 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.
    (KLuehrs, 17:40:03)
  * OpenDaylight allows network elements to register, which allows
    OpenDaylight to maintain a database of network elements in its
    domain.  (KLuehrs, 17:40:52)
  * 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  (KLuehrs,
    17:43:10)

* MEF LSO Hackathon  (KLuehrs, 17:43:21)
  * 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
    (KLuehrs, 17:45:10)
  * LINK: https://wiki.mef.net/display/LH/MEF+LSO+Hackathon  (KLuehrs,
    17:45:16)
  * 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)  (KLuehrs,
    17:47:46)
  * NOTE: There will be no OPNFV LSOAPI project meeting next week,
    November 9 - 13 due to OPNFV Summit.  (KLuehrs, 17:48:27)



Meeting ended at 17:48:30 UTC.



People present (lines said)
---------------------------

* KLuehrs (20)
* collabot (4)



Generated by `MeetBot`_ 0.1.4