08:07:56 #startmeeting Tacker 08:07:56 Meeting started Tue May 19 08:07:56 2020 UTC and is due to finish in 60 minutes. The chair is hyunsikyang__. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:07:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:07:59 The meeting name has been set to 'tacker' 08:08:01 yasufum: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 08:08:11 Thanks 08:08:18 sorry I just try test it.. 08:08:23 that's okay 08:08:28 thanks 08:09:06 What is the today's topic? 08:09:14 I would like to continue discussion for networking-sfc today 08:09:19 can we discuss about networing-sfc? 08:09:21 ok 08:09:35 #topic networking-sfc 08:09:35 although takahashi-san does not join yet 08:09:53 #link https://etherpad.opendev.org/p/tacker-meeting 08:10:46 Our team try to cover networking-sfc part:) 08:10:55 hi 08:10:58 I am here from the neutron perspective. I originally raised networking-sfc topic to takahashi-san internally. 08:11:02 Hi amotoki 08:11:06 hi 08:11:10 hello 08:11:16 hi 08:11:17 hi 08:11:19 hi 08:11:26 go ahead :) 08:12:26 So, we will start it from the current status of networking sfc in tacker. 08:13:15 As a perspective of tacker, it is important features. So, I want to maintain it. 08:14:07 Do you mean as a core reviwer? 08:15:18 yes. 08:16:05 I can contribute as a +1 reviwer. 08:16:55 thx. It is good feature for tacker. We will start to check networking sfc feature in tacker internally. 08:17:19 amotoki, do you know how many contributers required for maintaining the project roughly? 08:17:42 yasufum: roughly speaking, there is NO contirbutors specific to networking-sfc. 08:18:06 neutron core team is helping the sfc reviews from the maintenance perspectivve 08:18:24 but the neutron core team have no good knowledge on sfc features. 08:18:45 it just covers gate failures and topics which are neutron-wide. 08:18:50 that's the current status. 08:19:36 so it would be nice if folks from tacker team can be involved in reviews in networkng-sfc. 08:20:05 yasufum: sorry. I misunderstood your question. 08:20:18 your question was how many contributors are required. 08:20:24 yes 08:20:35 I am not sure the right number 08:21:26 I think we can do small start just by checking reviews and so on together. 08:21:38 right 08:22:32 perhaps what we need is volunteers for reviewing/triaging bugs from feature perspective. 08:22:55 neuron cores continue add +2 for merging, right? 08:23:20 amotoki, If you know the feature link, please update it here. 08:23:28 yasufum: what do you mean by "add +2"? 08:23:59 I wonder how we check and merge patches 08:24:41 Merging patch requires one or two +2 basically, right? 08:24:53 yasufum: yes, +W right is needed. 08:24:57 there are several options to start. 08:25:35 the one is to consider +1 from folks familiar with sfc (like tacker team) as +2 and merge patches by the neutron team 08:25:51 the other is to add tacker team to the netwokring-sfc core team. 08:26:22 I see 08:26:38 I though second one, but I understand it can be flexible. 08:27:39 the first one would be a step to networking-sfc core reviewers. 08:27:59 the second option sounds like a co-maintenance of netwokring-sfc by neutron and tacker team together. 08:28:13 I have no strong option on this. 08:29:34 co-maintenace sounds a good option. 08:29:40 for example, the horizon team do similar for horizon plugins. 08:30:17 Sorry for late... 08:30:20 hi 08:30:25 Hi 08:32:48 I am not sure about scheme of co-maintenance, but it seems good. 08:34:34 what are unclear? for example, what roles are expected? 08:34:52 yes, that’s right 08:35:33 but I can learn from 08:36:02 from the neutron governance perspective, we have point of contacts per sub project like networking-sfc 08:36:11 https://docs.openstack.org/neutron/latest/contributor/policies/neutron-teams.html#sub-project-lieutenants 08:37:08 it is called as "Lieutenants " in the neutron team 08:38:15 thanks 08:38:27 Like a before, why don't you take a role of lieutenant? yasufum? 08:39:05 the reason I raised this topic this time is we didn't do it officially. 08:39:36 I talked with dharmendra directly and he said he could be a contact for netwokring-sfc in Ussuri cycle. 08:39:54 ah. 08:40:03 I think it is better to disucss it as a team. 08:40:13 OK. I thought he left this team:) 08:40:27 yeah, he changed companies during ussuri cycle. 08:41:38 hyunsikyang: I am not sure to make a time for the role now. 08:42:03 pls continue to talk on next meeting or tacker IRC. 08:42:14 personally (from my hat of neutron) it would be great if the tacker team is involved in development of networking-sfc. 08:42:35 I think so 08:42:57 thanks amotoki, we are trying to join for that. 08:43:45 if dharmendra can do it continueously, just leave it. 08:44:01 and tacker team just support it. 08:45:26 let me summarize what the neutron team do on a stadium project. I think it helps better understanding. 08:45:31 Anyway, now tacker team have a consensus about joining networking-sfc, let's decide concrete plan for that. 08:45:40 yes 08:45:59 If you have a time, please share it anytime in tacker IRC. 08:46:12 hyunsikyang__: sure. what is better? 08:46:53 hyunsikyang__: I am usually not there, so I can join when needed. 08:47:06 s/what/when/ 08:47:40 ok. 08:48:06 I think you have more topics in this meeting. let's cover it later. 08:48:13 OK:) 08:48:27 thanks, amotoki 08:48:41 let's make a list for that later and decide it during the vPTG. 08:49:49 thanks. 08:50:06 yasufum, do we have more topic, today? 08:50:20 yes, 08:50:42 do you some other topics, everyone? 08:51:03 for next PTG, or patch review 08:51:08 or so 08:51:24 I don't have it. today. 08:51:56 let me ask about C-VNF topic in vPTG 08:52:20 #link https://etherpad.opendev.org/p/Tacker-PTG-Victoria 08:52:21 ok:) 08:52:56 I'm preparing a spec for CNF operation based on ETSI specifications 08:53:21 you mean that CISM? 08:53:31 we are also prepare it. if CISM is right. 08:53:41 Yes 08:54:28 I assume we can extend the existing Kubernete infra driver to support vnflcm related operation as VNF 08:54:34 right 08:54:41 So we are preparing it. 08:55:15 Now, kubernetes in tacker is not scalable, and not correspond to ETSI spec. 08:55:19 So, It needs it. 08:55:32 then how about sharing the specs before vPTG? 08:55:45 what is the mean of spec? 08:55:47 blueprint? 08:56:00 blueprint and spec for V cycle 08:56:08 okie:) good. 08:57:21 I'll talk to yasufum how to share our specs and let me discuss at IRC or next meeting 08:58:06 ok 08:58:15 thanks 08:59:12 does anyone add the networking-sfc topic to the vPTG etherpad? 08:59:13 I think it is OK to share your draft on etherpad if possible 08:59:24 If so I can add my note there. 09:00:13 sorry for interrupt.... 09:00:23 OK, I add it amotoki 09:00:23 no problem. it is welcome 09:00:48 takahashi-tsc: thanks 09:00:53 thanks all 09:01:30 can we wrap up because it is the end of the time? 09:01:45 ok Let's finish it. 09:01:49 if anyone has a topic 09:02:03 does not has a topic,sorry 09:02:24 thanks hyunsikyang 09:02:35 ok. let's finish it and if someone has a topic,let's talk in tacker IRC 09:02:36 #endmeeting