13:04:01 <rprakash> #startmeeting domino-models 13:04:01 <collabot> Meeting started Mon Apr 24 13:04:01 2017 UTC. The chair is rprakash. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:04:01 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 13:04:01 <collabot> The meeting name has been set to 'domino_models' 13:04:35 <rprakash> #chair uck bryan_att rprakash 13:04:35 <collabot> Current chairs: bryan_att rprakash uck 13:05:10 <rprakash> Is there a Gotomeeting link to call? or is it irc only meeting? 13:05:35 <uck> @rprakash somehow gotomeeting link is not working 13:05:35 <collabot> uck: Error: "rprakash" is not a valid command. 13:06:04 <uck> rprakash: shall we just use irc? 13:06:35 <rprakash> yes 13:07:11 <rprakash> Anyway the GTM links are not fixed yet 13:07:17 <uck> #info Ulas Kozat 13:07:32 <uck> it says invalid meeting ID 13:07:50 <uck> #topic E Release Plan 13:08:17 <rprakash> #link https://wiki.opnfv.org/display/domino 13:09:24 <rprakash> Should we look at resource orchestartion using kubernetes this time? 13:10:24 <uck> That can be a good idea 13:11:17 <uck> I was thinking couple of items: 13:11:33 <rprakash> #link https://wiki.opnfv.org/display/domino?preview=/2925446/2925447/opnfv_technical_discussion_-_domino_proposal.pptx 13:11:34 <uck> (1) Returning a workflow 13:11:43 <rprakash> #Ok 13:12:23 <rprakash> #you mean workflow generation? 13:12:34 <uck> as currently when publishing is completed Server only return success or failure code. Now it will also state which sub-template received by which domain. 13:13:13 <uck> It may be better not to say workflow, but extension to Publish RPC call. 13:13:45 <uck> (2) Domino HA? 13:14:28 <uck> (3) Kubernetes support 13:14:47 <rprakash> #info you mean template will contain vnf redundancy for HA? 13:15:31 <uck> #info no, it will create multiple Domino Servers for Domino HA 13:16:04 <uck> #info however what you say also is interesting!! 13:17:24 <rprakash> #info we need to scope and time is limited so state what and we will fill in how after some delibrationbs 13:17:29 <uck> #info Especially in the case of edge cloud, Domino can push the same template to many locations and returns the publisher the list of locations where VNFD is onboarded 13:18:25 <uck> #info Let's stick with template HA onboarding. 13:18:35 <rprakash> OK 13:19:01 <rprakash> about kubernetes shall we look at openretriever https://wiki.opnfv.org/display/PROJ/Project+Proposals+OpenRetriever 13:20:48 <rprakash> #inof this project was merged with some other don't recollect now but we can ask help from Amar 13:21:53 <rprakash> #info We state as a wishlist the Kubernetes orchestartion for now and if able to cover include that as one more target 13:22:04 <uck> #info Is this an installer project? 13:22:57 <rprakash> #info ok ignore Openretriever just focus on orchetsration for resource by kubernetes instaed of heat 13:23:01 <uck> #info what is the maturity level of tosca2kubernetes? 13:24:35 <rprakash> #info parser project did not complete that in D and we may have to look at ARIA then http://ariatosca.org/about/ 13:27:45 <rprakash> #Possibly if we use ARIA we can support better fetaures for templates including workflow, kubernetes resource orchetsration, but will need more thinking and not sure we have enough tyime or resource 13:27:45 <uck> #info does aria perform any translation? 13:29:04 <uck> #info the way tosca template vs. kubernetes yaml file represent are quite different 13:29:27 <uck> #info I mean how they represent a service 13:30:06 <rprakash> #info openstackplugin supports heat so translation seems to be part of that, but need to confirm 13:32:53 <uck> #info Maybe they do. Since they have their own "tosca" types, it may not be a big issue to translate from one to another 13:33:23 <rprakash> #info yes the apllication/service templates are different called blueprints but seems thy still use tosca node types and other elements links etc. 13:33:52 <uck> #info we can do a "requirements" type of documentation target maybe, rather than delivering a code 13:34:34 <rprakash> #info agreed that makes sense since we have no clue at this time on details of implementaions on any of the 3 listed work items 13:34:38 <uck> #info or as I said, we do not worry about translation and support kubernetes yaml input for distribution 13:35:24 <uck> #info when a file is published, Domino can automatically identify if it is a kubernetes file and then pick a domain that supports containers. 13:35:38 <rprakash> ok that helps but we do some analysis and documentaions first and see what can be delivered in E for coding and testing 13:36:06 <uck> sounds good 13:36:19 <uck> shall we finish up? 13:36:48 <rprakash> Sure unless Bryan is there lets wait if he jumps in for model? 13:37:18 <rprakash> #info Bryan do you want anything for models to discuss? 13:37:46 <rprakash> OK if he is not on irc lets close the meeting 13:38:03 <uck> okay. 13:38:17 <rprakash> #endmeeting domino-modles