04:30:44 #startmeeting tacker 04:30:45 Meeting started Wed Sep 20 04:30:44 2017 UTC and is due to finish in 60 minutes. The chair is gongysh. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:30:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:30:48 The meeting name has been set to 'tacker' 04:31:07 #topic roll call 04:31:10 hi 04:31:22 who are you guys here for tacker meeting? 04:32:28 o/ 04:32:34 hi gongysh 04:32:36 o/ 04:32:40 hi everyone 04:32:46 hi 04:33:19 we will start at 12:35 04:35:04 #topic bp 04:36:26 I have to leave after 30 mins 04:36:32 o/ 04:36:34 o/ 04:36:34 so we will have a short meeting 04:37:04 first thing I want to talk is bp in queens-1 milestone. 04:37:24 #link https://blueprints.launchpad.net/tacker 04:37:41 phuoc, hi 04:38:05 service-assurance-engine is replaced by vnffg-healing and vnffg-scaling, right? 04:38:05 i will commit some BPs these days 04:38:12 hi gongysh 04:38:29 that's right 04:38:48 ok, I will remove service-assurance-engine and put those into queens 04:40:20 o/ 04:40:42 phuoc, I have moved vnffg-healing and vnffg-scaling into queens 04:40:58 phuoc are you guys still working on them? 04:41:04 gongysh, thanks 04:41:34 We are working on that, but we have some problems need to figure out 04:42:02 ok, thanks 04:42:10 YanXing_an, https://blueprints.launchpad.net/tacker/+spec/vnffg-ns 04:42:19 what is the progress? 04:42:52 some delay on this 04:43:37 YanXing_an, we should work under moonlights to finish it. 04:44:25 for the bp, https://blueprints.launchpad.net/tacker/+spec/mistral-monitor-policy 04:44:44 YanXing_an, I hope nobody has started working on https://blueprints.launchpad.net/tacker/+spec/indirect-mode-vnfm 04:44:48 yeh, i will have time in these weeks 04:44:59 gongysh: YanXing_an, can i start on this ? 04:45:00 I will try to upload the codes these weekends. 04:45:34 diga, i just put the paper in google doc 04:45:50 diga, yes you can 04:45:52 YanXing_an: okay, can you share the link 04:46:05 diga, but I think you should investigate osm first. 04:46:10 https://docs.google.com/document/d/1jWj_k6Ctpr61N-GKsdfAq_YKnP83L6h7wHFKma8ahXI/edit?usp=sharing 04:46:11 https://docs.google.com/document/d/1jWj_k6Ctpr61N-GKsdfAq_YKnP83L6h7wHFKma8ahXI/edit?usp=sharing 04:46:11 https://docs.google.com/document/d/1jWj_k6Ctpr61N-GKsdfAq_YKnP83L6h7wHFKma8ahXI/edit?usp=sharing 04:46:11 https://docs.google.com/document/d/1jWj_k6Ctpr61N-GKsdfAq_YKnP83L6h7wHFKma8ahXI/edit?usp=sharing 04:46:11 https://docs.google.com/document/d/1jWj_k6Ctpr61N-GKsdfAq_YKnP83L6h7wHFKma8ahXI/edit?usp=sharing 04:46:14 YanXing_an: so that we can break out things in pieces to get started 04:46:24 and have a report on the google doc. 04:46:25 gongysh: okay 04:46:28 https://docs.google.com/document/d/14Nc9jV1XbodoI1uuuAU1aMrhCPWBFAAbPh2TRb5U2t8/edit?usp=sharing 04:46:28 YanXing_an: Thanks 04:46:35 diga, thanks 04:46:40 two links 04:47:01 last week, I have put two small bps 04:47:22 https://blueprints.launchpad.net/tacker/+spec/split-tacker-install-from-vim-target 04:47:44 gongysh: I will go through it 04:47:58 hope everyone here to read it and to know what tacker system is. 04:48:14 what vim is. 04:48:32 tacker can be installed from its managed vim. 04:49:03 that is the essential part the BP want to say. 04:49:15 okay 04:49:22 tacker can be installed independent from its managed vims. 04:49:57 another small bp is https://blueprints.launchpad.net/tacker/+spec/kolla-deploy-tacker 04:50:42 which will help new comers to set up a tacker system easily. 04:51:19 you guys can have a tacker system with this document quickly. 04:51:30 it is stabler than devstack way. 04:52:30 one new bp: https://blueprints.launchpad.net/tacker/+spec/containerised-vnfs 04:52:41 o/ 04:52:43 I have reviewed 04:53:18 janki, gongysh: I will make a new bp for K8s as VIM, separate with this one 04:53:19 gongysh: lots of BPs for queens :) 04:53:26 janki, maybe you can first write a doc about how to set up a k8s first. 04:53:51 If the process is good, containerised vnfs bp is the next step 04:54:04 gongysh, lets first emphasis on writing the bp.. 04:54:07 for supporting k8s type of c-VNF 04:54:30 phuoc, so your k8s vim is the first step, and then we will have containerised-vnfs. 04:54:53 gongysh, yes, exactly 04:55:01 ok 04:55:05 phuoc, ^ 04:55:51 janki, we need more meeting to define all requirements :) 04:56:08 please keep active involvement, make the job forwards. 04:56:14 phuoc, can you reply to our mail suggesting a time? 04:56:42 #topic open discussion 04:57:05 janki, sure I will do it asap :) 04:57:29 talk something if you have 04:57:41 phuoc, ack.. 04:57:55 gongysh: I believe call for paper for next summit is opened 04:58:13 what summit? 04:58:20 you mean vancouver summit? 04:58:36 yeah 04:59:27 diga, do you have link? 05:00:13 I got a mail on cinder maillist, may be we shoiuld keep an eye on these things 05:00:43 gongysh: will send me details, it was just a mail, need to find a link 05:00:55 diga, ok, thanks 05:01:10 gongysh: welcome! 05:01:44 gongysh: just one questions, how we can debug tacker if we install using kolla 05:02:18 * gongysh search kolla documentation 05:02:42 diga, https://docs.openstack.org/kolla-ansible/latest/user/kolla-for-openstack-development.html 05:03:11 gongysh: okay, will go througith 05:03:56 diga, need this patch: https://review.openstack.org/#/c/497544/1 05:04:06 gongysh: okay 05:04:37 I will write a doc about it. 05:05:00 yeah 05:05:38 anything else? 05:06:01 nothing from my side 05:06:09 YanXing_an, https://review.openstack.org/#/c/504758/ 05:06:10 YanXing_an: I will ping you seperately 05:06:20 I have updated the doc 05:06:25 please have a look at it. 05:06:56 ok 05:07:11 diga, ok 05:07:45 hi guys, it seems tacker is coming into container time, so please get some skills of docker and k8s. 05:08:30 gongysh, that's right :) 05:08:32 kolla and kolla ansible is also coming into our skill scope. 05:08:41 I will look at kolla too 05:09:05 2 mins to go 05:09:07 gongysh: I worked on kolla sometime back :) 05:09:25 diga, so please review our kolla doc. 05:09:33 gongysh: yeah 05:09:45 I have to quit, see you ~ 05:09:56 ok, thanks everyone, please keep reviewing and contribution 05:10:00 bye 05:10:07 #endmeeting