13:45:30 <kennypaul> #startmeeting vf2f 2018-02-07 13:45:30 <collabot`> Meeting started Wed Feb 7 13:45:30 2018 UTC. The chair is kennypaul. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:45:30 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic. 13:45:30 <collabot`> The meeting name has been set to 'vf2f_2018_02_07' 13:45:34 <kennypaul> #chair phrobb, BinY_, SteveT 13:45:34 <collabot`> Warning: Nick not in channel: BinY_ 13:45:34 <collabot`> Current chairs: BinY_ SteveT kennypaul phrobb 14:01:52 <SteveT> #info Stephen Terrill, ERicsson 14:02:25 <Zhaoxing_Meng> #info Zhaoxing Meng, ZTE 14:02:52 <cdonley> #info Chris Donley Huawei 14:06:36 <SteveT> #topic MSB Tutorial 14:06:51 <SteveT> #info Huabing Zhao presented the MSB tutorial 14:08:25 <SteveT> #info Huabing also offered that the tutorial can be given to projects upon request. 14:22:36 <SteveT> #info MSB is offering a RPC call, so if there is no exception it should be understood that the message is recieved by the reciever 14:33:53 <kennypaul> #info just a comment for Huabing Zhao... this is the scenario.. the receiver received a message, but the return confirmation communciation is lost. In this case, the sender did not get a successful response. Then, the sender may try to send the same message again even though the receiver received the messge. I guess MSB inherits the HTTP/HTTPS messaging reliability issue. I will contact Huabing off-line. 14:36:17 <SteveT> #topic Modeling subcommittee 14:37:24 <SteveT> #info There are several sub topics here. 14:38:15 <SteveT> #info The first subtopic is Service IM 14:45:06 <SteveT> #info next sub-topic is resource IM 14:45:24 <SteveT> #info PNFD is not defined yet, but it is consiered as a resource IM. 14:49:42 <SteveT> #info there were questions about the relationship between the service and the service component. The response was the service was more related to the customer facing service 14:50:18 <SteveT> #info Not all artifacts are yet captured in the VNF descriptor 14:53:10 <SteveT> #info the resource model is defined in a uniform way (irrespective of whether it is managed by VF-C or APP-C) 14:56:46 <SteveT> #info There was a request to discuss the modelling with the projects at a project level as well. 15:01:15 <SteveT> #info There was a question whether a service that is an infrastructure servce can be used as a service comonent in another service. The answer was that it was thought that substition could use. And it also said a service can be nested to be part of another service. 15:02:20 <SteveT> #info Next sub-topic was data model aspects 15:05:43 <SteveT> #info All datamodel information is available in the modelling sub-committee wikis 15:12:32 <SteveT> #info Discussion about aligning with standards or go for a comosite resource approach as described in the wiki. 15:13:51 <SteveT> #info next subtopic is parser centralization 15:15:30 <SteveT> #info there is a weekly call for the parser tiger team. they are preparing the user stories and requirements. Will look at API access of this parser as a service, exception handling interactation, can a placeholder be created in modelling project to on-board various parsers and abstract them with an API. PoC activities. 15:17:05 <SteveT> #info the PoC is to see if there if the centralized parser makes sense. 15:19:21 <SteveT> #info - question was do the PTLs that are using teh SDC parser today agree they need another library that is remoted. Response. The response was that the OPNF Parser is a good standard parser. 15:20:01 <SteveT> #info it was indicated that the OPNFV parser supuports yaml 1.1, with yaml 1.2 in developement 15:22:26 <SteveT> #info when considering java libraries, consider both python as well as java 15:23:31 <SteveT> #info correction - that was when considering common libraries, consider both python and java 15:25:38 <kennypaul> #link for video https://wiki.onap.org/display/DW/Modeling+tools 15:25:51 <SteveT> #info next subtopic was a papryus tutorial, but suggested to look at the provided link 15:26:08 <SteveT> #info There was a request for contact for all components. 15:33:53 <SteveT> #topic Usecase Subcommittee Review 15:33:58 <SteveT> #info presented by Alla 15:49:50 <SteveT> #info PNF is configured with SDNC as its a L1-L3 PNF 15:58:16 <SteveT> #info PNF support for changemanagement has not discussed change management and scaling. Not expected to be in Beijing. 16:03:46 <SteveT> #info It was noted that there is no SDC Epic for pnf support, SO neither 16:07:33 <kennypaul> #endmeeting