08:01:46 #startmeeting tacker 08:01:46 Meeting started Tue Nov 29 08:01:46 2022 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:01:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:01:46 The meeting name has been set to 'tacker' 08:02:18 #link https://etherpad.opendev.org/p/tacker-meeting 08:02:41 There are five items on the etherpad today. 08:02:50 ueha: can you start from your update? 08:03:17 Okay, I will start 08:03:24 I have just information sharing about Legacy API deprecation. 08:03:47 I have emailed to Discuss-ML on Nov 25, and no one replied to this thread as for now. 08:03:54 https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031307.html 08:04:08 That's all from my side. 08:04:31 any comment? 08:04:41 No reply on the thread? 08:04:54 Yes 08:05:00 ok 08:05:37 go on to the next 08:05:57 Next two items are mine, but same topic actually 08:06:53 Although I've asked mapreetk to change unmaintained bugs status, I also started to the task. 08:07:20 Because it's better to do in parallel. 08:08:04 Basically, I'm changing the status to "Won't fix" for old items. 08:08:34 Around 2020 or before ones. 08:09:41 However, there are some items the current status is not clear, for me at least. 08:10:20 So, I'd appreciate if you help me to clarify them. 08:10:35 I've just listed up the bugs on the etherpad. 08:11:05 Let me know by leaving some comment on each report if you know something about. 08:11:26 That's all for the second item. 08:11:32 Any comment? 08:12:35 Thanks for your work! I will check with my colleague. 08:12:40 thx 08:12:55 good 08:13:21 The third item of mine is also the chaning the status. 08:13:34 Which one should we update, launchpad or etherpad or both? 08:14:03 On launchpad is enough. 08:14:19 Okay, I got, thank you! 08:14:50 ok 08:15:35 There three items for which I can change to "Won't fix" but not so sure. 08:16:46 s/I can/I think we can/ 08:17:29 Please tell me if there is a bug we shouldn't change the status. 08:17:42 on launchpad 08:18:14 If no comment until next week, I'll change the status. 08:18:21 That's all. 08:19:50 If no one has comment, go to the next item. 08:20:13 good 08:20:41 manpreetk: can you share about your update for bug triage activity? 08:20:49 Yes!! Thanks 08:21:17 First of all would like to thanks yasufum for helping hand. 08:21:34 you're welcome. 08:21:39 This update is regarding bug triage activity reporting process. 08:22:19 Added a bug triage roaster etherpad [1] and submit report of bug triage done last week [2]. 08:22:19 [1] https://etherpad.opendev.org/p/tacker-bug-triage-roaster 08:22:19 [2] https://etherpad.opendev.org/p/tacker-bug-triage-20221128 08:22:19 The bug triage reporting or recording in etherpad can be optional. IMO, it will be helpful if we need discussion or keep track of bugs (open/in-progress) status. But would like to here team's opinion. 08:23:32 Thats all for this topic. 08:24:50 Is there any rules for changing the status to "Invalid"? 08:25:13 Because we agreed to change it to "Won't fix" at once. 08:26:44 There isn't any specific rule, i changed those bugs which were irreproducible in master branch to "Invalid". 08:27:58 Umm if you suggest i ll change them to "Wont fix". 08:28:20 I don't mean so actually. 08:29:05 I've just though it's better to have some more correct rules if possible. 08:29:59 Guess that will be helpful, we can update the same in https://etherpad.opendev.org/p/tacker-bugtriage 08:30:15 But I've also understood that it depends on each cases and difficult to. 08:32:05 Anyway, we don't need to so serious about which category is the most appropriate for too old bugs actually. 08:32:49 Yes agree!! 08:33:27 Any other comment, guys? 08:33:42 Or we can go to the next item? 08:34:21 good 08:34:38 manpreetk: let's move on to the next one. 08:34:45 Yes please. 08:35:14 This is regarding migration of tacker CI/CD jobs to Ubuntu Jammy (22.04). 08:35:20 As per OpenStack TC discussion, we need to run at least one job on Focal which can be removed in next cycle. 08:35:44 Would like to seek Tacker team's opinion whether we should run sol or sol-v2 gate jobs in focal? 08:35:44 Additionally once we select between above shared choices, do we need to run sol-kubernetes or sol-v2-kubernetes? 08:36:19 ueha: do you have any comment? 08:37:43 Or anyone? 08:38:03 IMO, both sol-v2 and sol-kubernetes-v2 are appropriate. What do you think others? 08:38:58 +1 08:39:08 I basically agree, but not for both. 08:39:28 yeah maybe we can skip kubernetes one? 08:39:32 It just a short term support for focal. 08:40:40 and don't need to have several tests for that. 08:41:01 In other word, simple is better for maintenance. 08:41:05 What do you think? 08:42:16 Does this mean that we don't need to check the operation of VIM type supported by Tacker on an old OS? 08:42:32 yasufum: You mean to run few test cases in the focal gate job?? 08:42:38 I think so. 08:43:58 I think focal is not a mainstream anymore. 08:45:35 If so, I agree that the sol-v2 test is enough for maintenances. 08:47:44 Any other comment? 08:48:40 good 08:48:44 Thanks for discussion will update the conclusion in etherpad, as well push separate patch for focal jobs. 08:49:06 manpreetk: Many thanks for your work for migrating to jammy! 08:49:21 Your welcome!! 08:50:05 All items done for today 08:50:24 But do you have any other topic? 08:50:39 for asking review or so? 08:52:53 Thanks and Bye! 08:53:00 good 08:53:16 So, let's close this meeting. 08:53:22 bye! 08:53:28 Thanks, bye! 08:53:32 Bye!!! 08:53:35 Thanks 08:53:38 bye 08:53:51 #endmeeting