16:02:59 <KLuehrs> #startmeeting LSOAPI
16:02:59 <collabot> Meeting started Thu Sep 10 16:02:59 2015 UTC.  The chair is KLuehrs. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:02:59 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:02:59 <collabot> The meeting name has been set to 'lsoapi'
16:03:06 <KLuehrs> #chair Kevin Luehrs
16:03:06 <collabot> Warning: Nick not in channel: Kevin
16:03:06 <collabot> Warning: Nick not in channel: Luehrs
16:03:06 <collabot> Current chairs: KLuehrs Kevin Luehrs
16:22:47 <dneary> iben: I'm on IRC
16:22:56 <dneary> Not paying attention very much
16:23:20 <dneary> iben: VNFD
16:23:54 <iben> KLuehrs: is there a meeting happening here? I don’t want to step on it if so...
16:24:29 <iben> dneary: wound’t the VNFD be sort fo defined by the mano solution? I assume they don’t all support a standard format
16:24:51 <iben> not really defined but i meant determined
16:25:44 <iben> and is the VNFD used only when onboarding a vnf?  then maybe the mano solution keeps all the info in a database that is also non-standard?
16:29:50 <KLuehrs> #Topic LSOAPI Task List
16:38:11 <KLuehrs> #info Kevin shared a spreadsheet listing tasks for completing the APIs being developed for this project. The list of tasks are largely focused on completing the CRUD (Create, Retrieve, Update and Delete) lifecycle requirements for each of the APIs and expanding from the minimum set of attributes used in the prototype, to the full set of attributes.
16:38:31 <iben> i’m back - my internet cut out
16:49:18 <KLuehrs> #info Each of these tasks will be entered in the LSOAPI Jira project as an issue. OPNFV release management team set the goal of having all project tasks posted as Jira issues by tomorrow, Friday September 11.
16:52:49 <KLuehrs> #info The LSOAPI project tasks each represent work that any participant can do to help complete API development and meet Brahmaputra release.
16:57:01 <KLuehrs> #info MEF defines another set of attributes, called EVC per UNI, that have not yet been captured in a class in the LSOAPI project. The definition and implementation of the EVC per UNI class remains as a significant task for the project. Steve Saunders is investigating the EVC per UNI attributes and how they are used in the system and will present his findings next week. Alberto G is
16:57:02 <KLuehrs> interested in contributing to API development so will attend the presentation.
17:00:21 <KLuehrs> #info Another set of attributes to be included as a class are attributes for the path between UNIs. Attributes are defined for the EVC which incorporates each leg between UNIs but from the provisioning level a tunnel needs to be established between each UNI and to manage the lifecycle of each tunnel the EVC Path needs to be modeled and implemented as a class as well.
17:01:09 <KLuehrs> #Action  CableLabs will schedule a web conference allowing others to join the presentation about EVC per UNI attributes
17:01:12 <KLuehrs> #endmeeting