04:32:13 #startmeeting tacker 04:32:14 Meeting started Wed Oct 25 04:32:13 2017 UTC and is due to finish in 60 minutes. The chair is gongysh. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:32:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:32:17 The meeting name has been set to 'tacker' 04:32:24 hi 04:32:33 o/ 04:32:33 o/ 04:32:37 o/ 04:32:44 o/ 04:32:48 o/ 04:32:52 dkushwaha, haha. welcome back 04:33:15 gongysh, thanks, long time stuck in client request 04:33:39 ok 04:33:44 lets start 04:33:50 #topic bp 04:34:24 phuoc, do you have any stuff to discuss for your two bps? 04:34:34 yes 04:34:42 the first bp, Kubernetes as VIM 04:35:25 I will remove using fernet key, use only use barbican to encrypt secret information 04:36:00 the second bp, I will make spec in Heat translator to make it meet to Tacker requirements for containerized VNF 04:36:44 gongysh: phuoc: I have updated the spec with changes as per the comments 04:37:02 phuoc: yes, we have to add spec in heat translator for k8s support 04:37:27 phuoc, the direction is fine for me. 04:37:41 Hi All, 04:37:53 trinaths, hi 04:37:55 gongysh, about add new container VNFM, do you have any suggestion? 04:38:00 hi trinaths :) 04:38:17 trinaths, hi:) 04:38:24 phuoc, you are talk about your 2nd bp? 04:38:27 talk -> talking 04:38:44 container VNFM ? 04:38:53 gongysh, yes 04:39:27 hi, gongysh phuoc MinWookKim :) 04:39:36 phuoc the heat-translator is not in the charge of tacker team 04:40:12 we should talk to zala for heat-translator 04:40:25 if we use it, we have to first do bp in heat-translator, and then do bp in tacker 04:40:40 yes 04:40:47 I think we should push it in Heat translator 04:41:04 I think we have tosca-parser and then do tosca-translator in our own way. 04:41:05 heat-translator is the perfect place. 04:41:31 phuoc: that way the code is re-usable by other projects. 04:41:37 I don't think so. heat-translator, the name hints, is to translator from tosca to hot 04:41:42 trinaths: +1, I will also go with heat translator 04:42:07 you guys are enlarge the heat-translator scope. 04:42:39 tosca-parser and heat-translator are sub projects to heat. we can have suggestions from Heat guys for this. 04:43:03 comments ? 04:43:07 gongysh, some guys from heat translator agreed to expand the heat translator scope 04:43:11 yes, we should talk to heat team and then come to conclusion 04:43:34 I asked Boh and Zala about it 04:43:36 in my opinion, first do tosca-translator in our own repo, and then push to related lib projects. 04:44:17 gongysh: you mean to avoid dependancy from start ? 04:44:33 gongysh, it can be the good way 04:44:35 gongysh: you want to implement it in tacker first 04:44:49 because if we start with Heat translator, it will take so long time 04:44:58 diga, yes 04:45:10 gongysh: okay 04:45:42 do you know at the beginning nova has all of the stuff, and then the network, volume is split from it. 04:45:51 I will think through this because how much it will take to implement it in heat-translator, it all depends on it 04:46:01 gongysh: there are two ways IMO, [1] develop the code for translate within taker and later move it to heat. [2] first develop in heat and then use the lib in tacker 04:46:38 but one thing we should get from heat-translator is, we can have full tosca parser support from other project also 04:46:40 if we use [1] we may spin the wheel where we need to fix issues ourselves when ever there are requirements and changes 04:47:20 trinaths, agree for 1 04:47:21 then using [1] writing translator might be good for now, but moving forward, it might not be the motive of the tacker team. 04:47:28 yes, that's the major problem here 04:47:40 trinaths: +1 04:48:12 so if [2] is considered, we can offload the translator issues to heat team after we or heat collaboratedly develop the translator and let heat manage the things 04:48:44 trinaths, heat-translator is not heat/ 04:48:51 that way [2] tacker as a MANO project can focus more on its essential future requirements rather than library fixex. 04:49:08 gongysh: agree. its a subproject from heat. 04:49:10 but if we follow [2], then we can develop generic translator which can be used for other projects also 04:49:20 with the help of heat 04:49:51 heat translator has few guys 04:50:09 if we want to push it, we have to get involve :) 04:50:26 IMO, its better to first discuss with heat guys 04:50:28 phuoc, the decision is do it in our own repo first, depends on tosca-parser project. 04:50:39 Guys, can I suggest one thing, We should talk to heat/het translator team first then we should decide 04:50:42 phuoc: we have to. that is the easy way. s 04:51:10 phuoc: please take this as an action-item and conclude this asap. 04:51:35 trinaths, ok I will do it soon 04:52:18 phuoc: its our initial priority.. 04:52:43 gongysh, can you approve this https://blueprints.launchpad.net/tacker/+spec/kubernetes-as-vim 04:52:48 phuoc: You need some help, let me know 04:53:47 diga, yes its huge work for me 04:53:54 phuoc: as gongysh said, we can also implement the translator in our code base. but it will contradict Tacker motive. 04:54:25 phuoc: already got involved in this and going through heat-translator code base also :) 04:55:32 trinaths, I will make a discuss with Zala and choose the best way 04:56:07 phuoc, my strategy is to do the parser first in our own base, and the put it into other project if needed. if the parser code is just one or two files, maybe we will not split it anyway. 04:56:12 ok, next bp 04:56:41 phuoc, I will +2 after my comment is fixed. 04:57:01 gongysh, thanks 04:57:07 and do you guys have tested the devstack script yet? 04:57:32 I failed because of the ability access to google related site. 04:57:59 gongysh: this one ? https://review.openstack.org/#/c/508559/ 04:58:33 yes 04:58:50 trinaths, have you? 04:59:26 gongysh: no.. 04:59:57 diga, do you have guys to test it? 05:00:15 gongysh: okay, will take a look at it 05:00:42 diga, ok, if it is tested, we can merge it as soon as possible. 05:00:48 diga, thanks 05:01:11 gongysh: yeah, i will test it by tomorrow 05:01:30 YanXing_an, hi 05:01:37 gongysh: i will test and reply my comments 05:01:40 hi 05:01:59 do you have any to talk about indirect mode and vnf with vnffg? 05:02:34 I have saw the comments in indirect mode spec 05:02:42 will update it 05:03:33 YanXing_an, I think we can apply your spec with container VNFM 05:03:39 and what about vnffg? 05:03:50 phuoc: no hurry. 05:03:56 and for vnffg in ns, will try to push the first patch next meeting 05:04:13 phuoc: lets complete this, mean time we can have indirect-mode ready. 05:04:45 trinaths, I mean in the future, not now :) 05:04:54 haha 05:05:06 gongysh: I want to introduce one of my company colleague 05:05:10 dkushwaha, can you start the policy mistral action tasks? 05:05:31 gongysh, yea, i will resume it now 05:05:45 phuoc: :) 05:05:59 dkushwaha, thanks 05:06:24 next bp 05:06:30 MinWookKim, hi 05:06:39 gongysh, hi 05:07:17 any think to talk about you AMP spec? 05:07:50 https://review.openstack.org/#/c/505466/ 05:08:19 I'm sorry, Actually security has not yet been considered. 05:08:30 For security, I will update the content after review. 05:09:37 and also to consider how the system will run if scale, respawn action is trigger backer to tacker system. 05:11:00 I'll update you soon. 05:11:27 who is interested in the AMP policy can help to review this spec patch. 05:11:59 I find Yan Xing an has done one review 05:12:05 i will review it 05:12:16 dkushwaha, thanks 05:12:32 tung doan is not back for a long time, 05:12:46 I think he will be interested in it too 05:12:51 We are also working on code for scale and respawn actions for the trigger. 05:13:13 MinWookKim, ok great 05:13:13 I think so 05:14:02 who know where is tung doan? whether will he be back to join us? 05:14:43 gongysh, he moved to another project and busy with it 05:14:50 i think, he shifted to Germany 05:14:52 I will notice him :) 05:15:14 o/ 05:15:26 hey gongysh 05:15:35 janki, hi 05:15:46 that is all for bp review 05:15:54 #topic coding 05:16:13 https://review.openstack.org/#/q/project:openstack/tacker 05:16:13 hi janki :) 05:16:24 we have some code patch in queue 05:16:24 phuoc, heyyy 05:16:26 not much 05:16:29 hi janki 05:16:38 YanXing_an, hello 05:16:42 please have your time to have a look at. 05:17:06 Dimitrios Markou is working hard, we should support him :) 05:17:11 https://review.openstack.org/#/c/509687/ 05:17:24 phuoc, you are right. 05:17:25 phuoc: +1 05:17:37 I see some his work is very helpful 05:17:47 dkushwaha, you have this +2, how do you think if we merge it? 05:19:27 gongysh, i haven't tested, but looks fine to me 05:19:37 dkushwaha, ok 05:19:52 I have to read the related doc and then merge it. 05:20:37 https://review.openstack.org/#/q/owner:%22Dimitrios+Markou%22+status:open 05:20:53 YanXing_an, there are two related to vnffg 05:20:59 gongysh: Let me introduce my colleague from my company, as we have very less time left 05:21:13 could you please help to review them? 05:21:31 #topic open discussion 05:21:34 gongysh, ok 05:21:36 gongysh: msk will be working with me on Tacker 05:21:37 diga, your time 05:21:43 gongysh: yes 05:22:25 msk? 05:22:26 msk (Mohsin) is a architect with having more than 10 years of exp in storage and networking domain 05:22:42 diga, I can't see him 05:22:44 is he/she at the channel? 05:22:45 diga, is he here? 05:22:56 yeah, he got disconnected 05:23:07 he is joining again 05:23:22 now he joined as mohsin 05:23:23 welcome mohsin 05:23:37 welcome to tacker mohsin 05:23:38 Thank you :) 05:23:42 welcome mohsin to Tacker :) 05:23:48 mohsin: hi :) 05:23:49 welcome, mohsin 05:23:53 diga, welcome the senior team member. 05:23:57 mohsin, hi 05:24:01 welcome mohsin :) 05:24:10 mohsin: please introduce 05:24:24 if we are doing wrong, please help to speak loudly. 05:24:25 Thanks all 05:24:43 :) 05:24:48 currently i am working with VMware based NFV platform 05:25:03 looking forward to contribute in Tacker 05:25:16 nice 05:25:27 mohsin, could you please talk some thing aoubt vmware nfv platform? 05:25:35 sure 05:25:53 does it have MANO part? 05:26:04 yes 05:26:23 gongysh: they have their own mano based NFV orchestrator 05:26:35 vmware publishes its reference architecture based on MANO 05:27:09 mohsin, in which company you working? 05:27:17 mohsin, if it is ok, share us some URL to learn. that will help to save a lot time. 05:27:50 dkushwaha, he is working along with diga. 05:27:55 dkushwaha: He is with Calsoft inc. same company I am working with now 05:27:55 dkushwaha, I think the same company with Diga :) 05:28:06 https://www.vmware.com/pdf/vmware-validated-design-20-reference-architecture-guide.pdf 05:28:07 phuoc: :) 05:28:17 mohsin, great 05:28:19 aah, got it 05:28:31 it is the open link from VMware which describes its ref architecture w.r.t MANO 05:28:35 2 mins left 05:29:25 mohsin: its aligned to ETSI NFV architecture ? 05:29:32 look forwards to progress within next week. 05:29:32 who all going to summit? 05:29:40 thanks everyone. 05:29:50 I will 05:30:06 me too 05:30:18 #endmeeting