08:03:28 #startmeeting tacker 08:03:29 Meeting started Tue Feb 9 08:03:28 2021 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:03:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:03:32 The meeting name has been set to 'tacker' 08:04:04 We have two topics today from our etherpad 08:04:08 link: https://etherpad.opendev.org/p/tacker-meeting 08:04:56 LiangLu: Can you start? 08:05:14 yes 08:05:50 My topic is invite reviews for UT coverage patches 08:06:39 These patches aims to improve some existing tacker code's UT coverage 08:06:48 and here is the blueprint:https://blueprints.launchpad.net/tacker/+spec/improve-ut-coverage 08:08:10 I classified files by function, and set priority for each functions. 08:08:53 And I have uploaded 4 patches for high-priority files 08:09:40 I'd like to invite code review for these patches(links are written at etherpad) 08:11:23 thanks 08:12:11 and some of these patch have conflict at merge, and even 1 is failed to pep8 check.. It is helpful to review it by link order. (I will solve the problem soon :)) 08:16:13 It looks a little bit large amount of files… What do you think to divide it if it take a long time? 08:16:48 Because it might be hard to track your progress of the task. 08:17:21 Or does it takes not so much time to complete? 08:18:51 I agree with you, although I divided them into several groups(patches) by functional 08:21:00 it is still not a small mount for each patch, also the whole blueprint target is large 08:21:27 yes 08:22:40 At least, I want to finish High and Medium priority files at Wallaby release 08:23:10 OK 08:25:09 Please update commit message in your patches to add blueprint tag after you separate your blueprint. 08:25:31 Any other comment? 08:25:34 OK, got it 08:25:44 LiangLu: thanks! 08:27:28 Oops, I have forgotten to set topic … 08:27:38 I would like to go to the nex topic. 08:28:15 #topic heat-translator tosca-parser core 08:28:54 This is just FYI, I've confirmed that some members are already added into heat-translator/tosca-parser core team. 08:29:27 Was there any announcement on ML? 08:30:54 Hmm... maybe no, individual mail to each member in order to proposal. And I just confirm gerrit page. 08:33:14 At least, I can put +2 for tosca-parser. And we can see the core member on gerrit 08:33:15 https://review.opendev.org/admin/groups/1f7855baf3cf14fedf72e443eef18d844bcd43fa,members 08:34:04 OK, thanks 08:34:21 I have confirmed that I can do that as same. 08:34:50 Let's activate the projects! I'll thank Bob later. 08:35:11 thanks 08:35:51 Please continue to contribute for the teams 08:36:29 If no more comments, go to the third topic. 08:36:39 #topic FT for K8s-MgmtDriver 08:37:18 yasufum: thanks 08:38:17 I'd like to ask your comments for skipping FT for K8s-MgmtDriver. 08:38:53 Our team are now implementing K8s-MgmtDriver for K8s clusters on OpenStack-VIM. 08:39:18 Our patch is almost done, but we found it's tricky to implement FT for it. 08:39:34 There are two issues: 08:39:41 1. Not sure how to connect to VMs from tacker-controller 08:39:48 2. Not sure how to connect to the Internet from VMs 08:40:27 Both of them are highly depends on the Zuul env, and seems hard to achieve now. 08:41:16 So I'd like to upload our K8s-MgmtDriver as just a sample for MgmtDriver introduction document. 08:42:01 In that case, our K8s-MgmtDriver is published as sample in Tacker repo, and we don't have FT for it. Users can download our sample and try to run on their envs. 08:42:36 Do you have any comments or questions? 08:44:14 Did you already uploaded a WIP patch? 08:44:49 Yes, we have three WIP patches on the Gerrit. 08:45:38 I think I need to make those to be re-structured to be a single MgmtDriver file. 08:47:59 https://review.opendev.org/c/openstack/tacker/+/772693/1 08:47:59 This one and this parents? 08:48:15 let me see... 08:48:51 takahashi-tsc: Yes, exactly. 08:49:05 https://review.opendev.org/c/openstack/tacker/+/771434 08:49:10 https://review.opendev.org/c/openstack/tacker/+/771805 08:50:24 These three. 08:53:10 I planned to implement 5 use cases for K8s-MgmtDriver (deploy-k8s/HA k8s/Scale worker/Heal nodes/Pod affinity), but I'll put them in the sample. 08:57:52 Basically, we do not have to make functional tests for sample... From such point of view, are there any FT which still have problems? 08:59:03 No. So let me move to make the sample patch with documents for MgmtDriver. 09:00:56 OK... but It's just my opinion. I'd like to know others' opinion. 09:01:53 Yes, it's important to hear from others. How about you, other members? 09:02:22 It might the first case having such a samples in our doc, but I think it is OK. 09:03:11 Might be the second case. We have OpenWRT MgmtDriver for legacy implementaion. 09:03:32 (It seems not working, though.) 09:05:11 I agree with it 09:07:12 OK, thanks 09:07:39 It is the end of the time, but do you any other topic? 09:07:50 Just asking for reviewing. [Support CNF scale operations based on ETSI NFV] https://review.opendev.org/c/openstack/tacker/+/765786 09:08:16 There is a merge conflict now, so I will rebase and resolve merge conflict soon. Thanks! 09:09:00 OK 09:09:32 takahashi-tsc: Can you review this one quickly? 09:09:36 #link https://review.opendev.org/c/openstack/tacker/+/774388 09:09:54 Sure 09:10:19 it is for fixing recent errors in FT for nfvo separate 09:10:24 thanks 09:11:19 It seems enough today. 09:11:29 Thank you for joining. Bye! 09:11:38 bye! 09:11:46 thanks! bye 09:11:52 #endmeeting