08:04:43 #startmeeting tacker 08:04:44 Meeting started Tue Dec 15 08:04:43 2020 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:04:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:04:47 The meeting name has been set to 'tacker' 08:05:24 We have five topics on our etherpad today. 08:05:29 #link https://etherpad.opendev.org/p/tacker-meeting 08:07:01 My three topics are just FIY and asking review, it no need to discuss actually 08:07:47 Me too. my topic is also just FYI. 08:08:41 keiko-k: could you expain shortly? 08:08:49 yes 08:09:57 those 2 specs are planned in Wallaby cycle. However, because of the priority of development items from our team, 08:10:31 we postpone to develop those spec items in wallaby cycle 08:10:45 https://review.opendev.org/c/openstack/tacker-specs/+/759658 08:10:50 https://review.opendev.org/c/openstack/tacker-specs/+/759655 08:11:30 We will plan to implement them in X cycle or later. 08:13:07 thanks for sharing 08:14:33 we will update both existing blueprint and spec appropriately. 08:15:06 So right now I do not make the spec `abandoned` and 08:15:17 and not delete blueprints. 08:15:26 OK 08:15:45 That's all from my side. 08:16:15 I think there is no problem if it is not released in wallaby because no plans other features depend on them. 08:17:25 right 08:17:39 go to the next topic if there are no comments 08:18:07 #topic tosca-parser-heat-translator-installation 08:19:04 As I suggested in previous meeting, I have uploaded a patch to make install these packages from git repo. 08:19:25 It looks working fine. 08:19:39 #link https://review.opendev.org/c/openstack/tacker/+/765296 08:20:34 Please review and give a comment! 08:21:57 If no comments, go to the next topic. 08:22:28 #topic lower-constraints-issue 08:23:24 As you may know, we have had a failure in a test for lower-constraints 08:23:46 It is because of recent update of pip on zuul 08:24:22 version 20.3.1, in which new dependency resolver is introduced. 08:25:12 This failure is happened not only in tacker, but also other projects. 08:26:04 For tacker, I have already fixed for master branch, but I am not sure If we should fix on stable branches or not actually. 08:26:27 In addition, discussion for dropping lower-constraints test on ML. 08:26:33 is going on 08:27:08 So, I would like to consider while looking the discussion for making the decision later. 08:27:31 I appreciate if you comment, now or on etherpad later is OK. 08:27:54 Please refer 12th item for the details. 08:28:03 ok:) 08:29:02 thanks 08:29:29 any comment? 08:29:52 OK 08:30:18 My last item is tiny. 08:30:33 Next week is the last of our meeting this year. 08:30:56 We need to fix when we start in the next year. 08:31:42 I will update candidate date on etherpad later, so please your comment. 08:32:16 ok. Thank you for your contribution! 08:32:27 Sure, thanks. 08:32:36 I will announce on ML after decided. 08:32:49 sure! 08:33:10 takahashi-tsc: Please go to the next topic 08:33:19 Sure. 08:33:23 #topic add-new-ft 08:34:15 I'd like to propose to add new FT set. See https://review.opendev.org/c/openstack/tacker/+/766162 08:35:15 Main purpose is we need new test environments with some GrantAPI settings of Tacker. We should separate test env. 08:36:41 it can also solve FT time problem. 08:37:38 I remember that our FT time is about 2hours, it is near the limitation of OpenStack Zuul (3 hours) 08:38:21 In addition, I found a patch which purpose seems similar. https://review.opendev.org/c/openstack/tacker/+/766886 08:38:55 It is for K8s. I think it is also needed. 08:40:29 Discussion points are.. 1. Do you agree with this? 2. If yes, do we need some new rules or developer docs of FT? 08:43:04 In my opinion, I think that some part of supporting K8s cluster setup is not scope of MANO. But, we are implementing ths feature, we also need FT for that. At first, we listup the item for FT and then we can discuss what item we will support. 08:45:03 Thanks 08:45:54 I think adding new tests run in pallalel is nice idea to avoid timeout error. 08:45:58 basically 08:46:34 I aggree with that point:) 08:46:38 but now I am not sure about rules and documentation actually 08:48:14 I mean that docs which show the FT set list and their explanations. 08:48:54 List maybe e.g. "Standard", "Separated NFVO", and "Kubernetes". 08:49:35 I think developer can understand it checking .zuul.yaml. But it is better to explain to developers. 08:50:26 I'm not sure it is mandatory or not, so I want Tacker team's comment. 08:50:45 sounds good for me 08:51:04 I believe that is really nice for developers 08:52:09 I have just imagined it is helpful if we have sequence diagram or so to understand our test flow. 08:53:20 takahashi-tsc: anyway, I understand your suggestion 08:54:05 OK, so my plan is, first I add new FT set (https://review.opendev.org/c/openstack/tacker/+/766162), next is make draft docs of FT. 08:55:34 And I'd like to discuss contexts of FT docs with Tacker members. 08:59:07 Could you add your idea of how to organize the docs in 7th items on the etherpad if possible? 08:59:37 “Revise documents” from yoshito-ito 09:00:22 Sure, i wrote note now, And i'll update it later. 09:00:37 Thanks. I will check it. 09:01:59 If no more comments, I would like close this meeting. 09:03:04 thanks for joining 09:03:06 bye 09:03:11 bye 09:03:14 bye 09:03:21 #endmeeting