08:01:23 #startmeeting tacker 08:01:24 Meeting started Tue Jul 14 08:01:23 2020 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:01:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:01:27 The meeting name has been set to 'tacker' 08:02:25 Hello 08:03:17 I would like to check status of specs proposed at previous vPTG. 08:04:10 It is about one month and half from the event, but some specs are still remanined. 08:05:03 Are there still under working specs? Or ready to be merged? 08:05:46 I have 2 specs remained. 08:05:50 Sorry but my 2 specs are remained. 08:05:53 Could you tell me if you can answer at this time, or leave a comment in gerrit later[ 08:06:08 https://review.opendev.org/#/c/731715/ 08:07:18 Thank you for the comment about Robot specs, my team have already discussed it, I'll update the spec soon, probably tomorrow. 08:07:22 This spec needs community reviews. already got one +2. need to get another +2 08:08:12 I have two specs left and they might be updated in the detailed design process, I'll update the status later in gerrit. 08:08:14 https://review.opendev.org/#/c/731718/ this spec is WIP. this week I will fix it. So please review it. 08:08:59 Action Driver spec are almost completed, but I'll update some impact and work item by this week. https://review.opendev.org/#/c/740896/ 08:09:34 OK, thank you for sharing 08:10:13 keiko-k: For patches required another +2, I will ask cores to review it. 08:10:34 yasufum thanks! 08:10:42 I have 1 spec remained. 08:13:52 makoto-ha: Did you complete to fix all comments? 08:14:55 I just want to know about the current status. 08:16:40 yasufum: https://review.opendev.org/#/c/732146/ I'll update this week. 08:17:10 Thanks. I understand. 08:18:21 I have one more thing to share about patch reviewing. 08:18:47 networking-sfc 08:20:50 I have started to review patches of networking-sfc. It seems there are no patches required to be merged urgently. 08:21:23 However, there are several patches needed to be reviewed. 08:22:27 I would like to ask you also review these patches if possible. 08:22:35 I agree, some bug patch is remained. Sorry for the late but I start to review. 08:24:54 Thanks! Go forward step by step. 08:27:04 Thats all for today from my side. 08:27:36 Is there any topic sharing? 08:28:01 I'd like to share discussion about TST, sorry but not completed yet, but can I share current ongoing discussion? 08:28:17 Sure! 08:28:20 https://etherpad.opendev.org/p/tacker-meeting 08:29:34 L91- First, we start to write our Tacker's test strategy. , UT is same as before, FT is little difficult to discuss... So I'd like to our "compliance test". 08:29:53 I'd like to clarify our "compliance test" 08:30:59 In my opinion, compliance test should be the test code provided by ETSI NFV, and should not be changed. 08:33:05 And I want to ask TST members to make document about coverage which related to compliance, like L106- 08:34:22 Best documentation is full matrix table, but I think it is too large... At least, we need some document with which we can understand current TST code coverage. 08:35:40 You mean that you are going to ask ETSI TST to provide pretty formatted docs for understanding easily, right? 08:37:41 Let me confirm what coverage you mean. TST code coverage of TST definition? or TST code coverage of SOL definition? 08:38:38 Right. I think Tacker need/should show compliance coverage , and in my opinion, TST members should make base documentation for compliance coverage. 08:39:05 coverage means TST code coverage of SOL definition, I think. 08:41:16 OK, thanks. 08:42:14 I agree. We need to show our couverage of SOL specs, and the document will help us for it a lot. 08:43:24 I belive the document needs to be generated automated way like api doc because it may be changed oftern according to the branch update. 08:44:33 I agree. Making full document manually is difficult to continue... 08:46:12 Are ETSI positive to introduce some framework or way of autogeneration? 08:46:43 I'm not sure... But I should propose it. 08:46:49 I’m not sure how they are thinking 08:47:01 OK. understand. 08:47:11 It is one discussion point, thanks. 08:47:28 I believe it must be so helpful for tacker dev! 08:48:30 OK, at next TST meeting, I have 2 topics. 1 is above, making coverage document. Another is about input parameter, but it is still under discussing... I think we will update etherpad by Thursday. 08:49:49 If possible please make comment after I update etherpad. 08:50:39 Good. I will. 08:50:44 OK I'll check it. 08:50:51 Could you tell me when the next TST meeting will be held? 08:51:49 Actually today... But I skip. I'll join on 28th July. 08:52:19 I see, thanks 08:54:18 https://portal.etsi.org/Meetings.aspx#/meeting?MtgId=38457 08:54:23 This is meeting link 08:55:29 Can I share a small topic about implementation? 08:55:44 yes, please go a head 08:56:29 Related to my spec of adding Artifact API, LiangLu posted a patch. It is still WIP but I welcome feedback. 08:57:04 I've already made some comments. 08:57:26 https://review.opendev.org/#/c/739697/ 08:57:28 and here is the link https://review.opendev.org/#/c/739697/ :) 08:57:53 Thank you Liang! 08:59:37 I should thank you for starting the topic :) 09:01:04 We are running out of time? 09:01:39 Yes. I would like wrap up if everyoen is OK. 09:01:57 Nothing from me 09:02:12 Thank you for joining 09:02:16 bye 09:02:17 thanks 09:02:20 thank you 09:02:28 #endmeeting