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


Meeting started by KLuehrs at 16:00:05 UTC.  The full logs are available
at
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-08-27-16.00.log.html
.



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

* Status Update  (KLuehrs, 16:04:33)
  * CableLabs was asked by MEF to help organize the MEF LSO Hackathon in
    November in Dallas, TX  (KLuehrs, 16:09:58)
  * CableLabs shared proposed development road map leading up to the MEF
    LSO Hackathon  (KLuehrs, 16:16:29)
  * Lance H suggested for the first phase, implement IP transport
    network with GRE tunnel overlay for EVC implementation. Currently
    ability to provide Layer 2 service is not in place in all service
    provider networks (business services over DOCSIS), leveraging IP
    makes more sense.  (KLuehrs, 16:18:11)
  * Group was queried: can anyone provide access to a NetConf enabled
    MEF compliant device? No response.  (KLuehrs, 16:21:57)
  * James Kim from CableLabs shared MEF plans for the LSO Hackathon. MEF
    currently plans two sub-projects during the Hackathon: one based on
    OPNFV Connectivity Services LSO project work and one based on MEF
    Service Configuration and Activation project.  (KLuehrs, 16:27:51)
  * ACTION: James Kim to send Hesham El Bakoury from Huawei information
    about the MEF Hackathon  (KLuehrs, 16:29:54)
  * MEF LSO Hackathon goals (1) Contribute API development back to MEF
    specifications, (2) Contribute API development back to outside
    projects including OPNFV Connectivity Services LSO.  (KLuehrs,
    16:36:07)
  * Question: Can another controller be used, e.g., ONOS? James Kim
    responded that for the Hackathon time is limited for preparation and
    planning so we need to focus on OpenDaylight for now. Kevin Luehrs
    added that the APIs being developed within LSOAPI will eventually be
    able to interface via REST to other controllers  (KLuehrs, 16:44:24)
  * Kevin Luehrs shared the LSOAPI software architecture documentation
    wiki page.  (KLuehrs, 16:44:52)
  * Steve Saunders shared the API documentation being developed using
    RAML. When complete this will be posted to the LSOAPI /documents
    wiki page.  (KLuehrs, 16:45:29)

* LSOAPI Requirements  (KLuehrs, 16:51:03)
  * Concern: How does architecture of the software map to an
    orchestrator? The APIs northbound to OpenDaylight likely belongs in
    an orchestrator. The focus is on the APIs and we need to find a home
    for the APIs, e.g., in OpenStack.  (KLuehrs, 16:56:19)
  * LSOAPI project seeks people with OpenStack expertise to help define
    where the northbound APIs belong.  (KLuehrs, 16:57:51)
  * Comment: While the proof of concept focuses on Ethernet eventually
    the APIs may need to support other transport.  (KLuehrs, 16:58:54)



Meeting ended at 17:01:30 UTC.



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

* KLuehrs (19)
* collabot (4)



Generated by `MeetBot`_ 0.1.4