11:55:34 <kennypaul> #startmeeting July V-F2F-2017-07-26 11:55:34 <collabot> Meeting started Wed Jul 26 11:55:34 2017 UTC. The chair is kennypaul. Information about MeetBot at http://wiki.debian.org/MeetBot. 11:55:34 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 11:55:34 <collabot> The meeting name has been set to 'july_v_f2f_2017_07_26' 11:55:55 <kennypaul> #chair phrobb SteveT CaseyODL 11:55:55 <collabot> Current chairs: CaseyODL SteveT kennypaul phrobb 11:56:26 <kennypaul> #topic Usecase Subcommittee 11:58:57 <SteveT> #info Stephen Terrill, Ericsson 12:04:03 <SteveT> #info Alla Goldner presented the Usecase subcommittee slides. 13:03:59 <kennypaul> #info From Catherine Lefevre "SD-LAN vs SD-WAN: http://www.aerohive.com/solutions/use-case/Software-Defined-LAN.html 13:03:59 <kennypaul> SD-LAN white paper written by aerohive: http://media.aerohive.com/documents/Aerohive-Whitepaper-SD-LAN.pdf" 13:09:07 <SteveT> #info CLAMP and the clamp cockpit was presented 13:09:15 <SteveT> #info for clamp in vCPE and clamp in vVoLTE, the additions are identified and relevant contacts are identified. 13:09:22 <SteveT> #info Alla asked whether there were any concerns with the identified modifications for Release 1, and it was responded that this is assumed to be in R1. 13:09:32 <SteveT> #info A discussion indicated that the automated test of clamp in R1 for integration is considered as a stretch goal. 13:09:42 <SteveT> #info There was a dicussion about whether clamp has an interface for design to be called by auto test, or does it all have to be done by a gui. This was something that had to be got back to. 13:09:51 <SteveT> #info there was a discussion over the identified questions for the vCPE use case 13:10:01 <SteveT> #info One question was regarding multi-vim and heat. the resonse was that multi-vim is providing a compatible API for R1, which includes vanilla openstack compatible APIs. 13:10:13 <SteveT> #info the the inteface to SDC from CLAMP is not expected to have more changes for R1 (i.e.) the functionality to support clamp for vCPE is believed to be there. 13:10:21 <SteveT> #info vVoLTE UC set of remaining issues were discusssed. 13:10:33 <SteveT> #info SDC is believed to support the models for vCPE. 13:10:44 <SteveT> #info It was clarified that SDC supports import of VNFs modelled in tosca. There are some limitations in the tosca syntax, but scope to extend it. 13:10:52 <SteveT> #info It was clarified that SDC supports import of VNFs modelled in tosca. There are some limitations in the tosca syntax, but scope to extend it. 13:11:01 <SteveT> #info It was stated that it was a good idea take the vVoLTE czars and identify what is missing. 13:11:08 <SteveT> #info The idea was to take the vVoTLE czar and try to input it into SDC 13:11:14 <SteveT> #info R2 use case proposals are on the wiki. More UCs can be added by updating the wiki (R2 use cases) 13:11:19 <SteveT> #info it was raised that the UCs are there to drive functionality into onap, so that UCs that doesn't drive new functionality should not be a UC. 13:11:40 <SteveT> (sorry, I was updating the wronge channel, I have just transfered it over) 13:13:01 <SteveT> #topic SDC questions 13:26:26 <SteveT> #info There is work to do to align on terminology definitions 13:29:21 <SteveT> #info the Catalogue shown in the pictures is not quieried in runtime, instead the models are pushed to SO, VFC etc in design time. 13:31:06 <SteveT> #info there was a question about the YANG models. The response was that these are uploaded to SDC as an artifact, though it was indicated for these use cases the YANG models are not used 13:33:55 <SteveT> #info the virtual link is in the network service package 13:39:51 <SteveT> #info the SDC APIs are on the wiki 13:45:51 <SteveT> #info the gap analysis will be updated after reviewing the SDC APIs 13:46:21 <SteveT> #link https://wiki.onap.org/display/DW/SDC+API 13:47:12 <SteveT> #info huabing zhao presented slides on the SDC models for vVoLTE 13:51:30 <SteveT> #info some of the substition mapping is identified as a bug, the rest seems to be supported by needs to be validated capability by capability 13:58:03 <SteveT> #info the discussion proposed to have plan B using the seed code from open-o as model designer, and have this as standby. 14:07:11 <SteveT> #info It was noted that the VoLTE - SDC discussion will continue in the parrallel meeting. 15:11:20 <SteveT> #topic VFC and A&AI 15:16:21 <SteveT> #info new nodes are added to A&AI by extending the schema 15:18:43 <SteveT> #info the A&AI team is developing a wiki page under the A&AI project describing how to install, extend etc A&AI 15:34:56 <SteveT> #info for Release 1 there is a pragmatic approach for updating the model for release 2 perhaps looking at the use cases to also look at the impacts 15:36:54 <SteveT> #info v11 is the version of the schema for R1 15:39:24 <SteveT> #info the schema is expected to be updated at each major release. 15:48:22 <SteveT> #info non backwards compabile changes to the schema will result in a data migration 15:48:46 <SteveT> #topic blocker list 15:51:26 <SteveT> #link https://wiki.onap.org/display/DW/July+Virtual+Developers+Event+Blockers 15:52:11 <SteveT> #info Phill Rob displayed the identified blockers list, and it was updated with the team that needs to respond 15:58:53 <SteveT> #info It was said that if blockers are identified in the future, then the same page can be used as well. 15:59:31 <SteveT> #endmeeting