08:00:43 #startmeeting tacker 08:00:44 Meeting started Tue Aug 25 08:00:43 2020 UTC and is due to finish in 60 minutes. The chair is takahashi-tsc. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:47 The meeting name has been set to 'tacker' 08:01:51 I think we have 2 topics at least, TST from me and revise docs from yoshito-ito 08:01:59 Any other topics? 08:02:15 I have a topic about revising docs. 08:02:51 oh, takahashi-tsc has already mentioned it, thank you. 08:03:40 OK. Can we start from my topic? 08:04:29 yes, please! 08:05:09 OK https://etherpad.opendev.org/p/tacker-meeting 08:05:16 L30- 08:06:30 I've participated TST meeting, and STF join the meeting. STF seems a team who make test code. 08:07:18 Basically, STF team agree with our proposal. Especially response code and response header. 08:08:23 But discussion is still needed and the actual test improvement may be in W cycle period... 08:08:57 Today, I'd like to discuss L38. i.e. What Tacker team can do for TST. 08:09:40 In my opinion, Tacker should not do standardization work, but we can contribute our own test code to TST. 08:10:09 What do you think about it? 08:11:42 I agree. The standardization is not our (Tacker's) scope, but it's good to make feedback to TST. 08:12:18 I'm not sure how the contrubution of our test code will be. 08:14:35 I think I'll improve Robot code for Tacker team. And some of them can be shared with STF team. 08:15:53 OK, we can make bug reports to TST repository, which may be a simple error of Robot code or a wrong definition from SOL documents. 08:17:33 Agree. I think we proceed with it for "Tacker testing improvement", and share with STF/TST. 08:17:34 I agree too. It should be closed to feedback such as conditions to be met for the test code.Standardization should be left to the TST as a traditional role. 08:19:49 OK, thank you for your comment. I write these comment in etherpad. I'll plan to discuss it with TST team. 08:20:12 Thanks 08:20:28 If you have some other comment, please write in etherpad. 08:20:51 Did you discuss the "tag" strategy in ETSI repository? Now we can find "2.4.1" and "2.6.1" are provided, and also 2.7.1 and 3.3.1 seems in developement. 08:21:31 Yes. you are correct. "2.4.1" and "2.6.1" are provided and later version is under development. 08:22:20 I suggest that TST should decide "maintenance policy". And STF team agree with it. 08:23:09 Great. That is a important step. 08:23:25 I think they do not decide how to maintenance branch which is already released... 08:24:50 I think we need to discuss when to start to try their Robot code. Can we wait for the policy from TST or STF? 08:25:20 In my current development for using Robot, I'll just use version 2.6.1. But we should continue to discuss with the output of our development. 08:26:20 In V cycle, I'll complete first development as above, and improve each (Tacker and TST/STF) code in W cycle. 08:26:57 Great, thank you. I agree to use v2.6.1 first. 08:28:04 OK, can we move to next topic from yoshito-ito? 08:28:14 OK 08:29:03 I'm trying to revise Tacker documents. 08:29:52 I found we need to update the doc structure itself because now we have unclear index. 08:30:19 My proposal is shown in https://etherpad.opendev.org/p/tacker-meeting. 08:30:32 I welcome your feedback. 08:31:46 I've already created a new doc structure. Also, I mapped the existing docs to it and marked "TBD" for new required docs. 08:32:41 I have already checked out the proposal. I have no objection to it. 08:33:06 Great thanks! As you wrote, we start to writing testing guide especially Robot (L429-432) 08:34:19 Main topic is Robot, but we try to organize UT, FT and Robot testing. 08:35:06 Thanks! It helps me a lot. 08:36:02 I will create docs for ETSI NFV-SOL based implementation in Use Case Guide. 08:36:44 Yes, we and Tacker users need it. 08:37:15 After the discussion in etherpad, I will upload a patch to re-design the structure of docs. Also I will propose required docs as much as possible in V release. 08:38:36 I'm not familiar with the legacy Tacker implementation, so I welcome your help. 08:38:41 Thanks, basically seems good. And our team will also discuss and give feedback later. 08:38:51 Great, thank you! 08:39:39 OK, I'll also talked about updating legacy Tacker docs. 08:42:06 Thank you! That's all from me for today. 08:42:36 OK thanks. Any other topics everyone? 08:43:11 I have no topic. 08:45:02 OK, let's close the meeting. Thank you! 08:45:20 Thank you! bye! 08:45:38 #endmeeting