yasufum | Hi tacker team. | 08:00 |
---|---|---|
takahashi-tsc | hi | 08:01 |
ueha | Hi | 08:01 |
yuta-kazato | hi | 08:01 |
yasufum | #startmeeting tacker | 08:02 |
opendevmeet | Meeting started Tue Mar 7 08:02:33 2023 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:02 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:02 |
opendevmeet | The meeting name has been set to 'tacker' | 08:02 |
yasufum | #link https://etherpad.opendev.org/p/tacker-meeting | 08:02 |
yasufum | We have seven items on the etherpad today. | 08:04 |
yasufum | I'm not sure all topics done in this meeting, but let's start. | 08:04 |
yasufum | #topic Moving governance of tosca-parser | 08:05 |
yasufum | After discussions in the meeting | 08:06 |
yasufum | and internal ones in NTT, I've decided to move those two projs as described in | 08:07 |
yasufum | the ML thread and patch proposed recently. | 08:07 |
yasufum | I wounder we have almost no tasks for them, without tiny updates for maintenance. | 08:09 |
yasufum | Because we don't have any issues should be fixed soon for now. | 08:10 |
yasufum | I have no idea how we should maintain these proj now, but let discuss later if it's required. | 08:12 |
yasufum | That's all. | 08:12 |
yasufum | Any comment? | 08:13 |
yasufum | good | 08:13 |
yasufum | So, let's move on to the second topic. | 08:13 |
yasufum | It's just an announcement. | 08:13 |
yasufum | We've fixed Antelope release. | 08:14 |
yasufum | Thanks all for your contributions! | 08:15 |
yasufum | Although we have some patches remained for the release, discuss for them later in the fifth topic from yuta-kazato. | 08:16 |
yasufum | And third topic then, | 08:16 |
yasufum | #topic FYI: Forum session | 08:16 |
yasufum | Although I've already shared a draft of forum session we are going to register, | 08:17 |
yasufum | it's still opened and will be fixed at the end of this week. | 08:18 |
yasufum | So, please give your comment if you still have something to proposal.. | 08:18 |
yasufum | Thanks. | 08:18 |
yasufum | Do you have any comment? | 08:18 |
yasufum | good | 08:19 |
yuta-kazato | +1, thanks for drafts, I added some comments. | 08:19 |
yasufum | thx | 08:19 |
yasufum | So, skip 4th item and jump into 5th because there are the same. | 08:20 |
yasufum | #topic Proposal for Tacker Antelope RC2 | 08:20 |
yasufum | yuta-kazato: can you share your item? | 08:20 |
yuta-kazato | ok | 08:20 |
yuta-kazato | First, thanks for all your contributions and reviews in Antelope cycle. | 08:21 |
yuta-kazato | Refer to previous item "Patches remained for antelope", unfortunately some patches are unmerged in RC1 week.. | 08:21 |
yuta-kazato | #link https://etherpad.opendev.org/p/tacker-antelope-fixes-rc | 08:21 |
yuta-kazato | Therefore I propose that additional community support for RC2. | 08:22 |
yuta-kazato | We have already informed the status of remained patches to the release team and thanks PTL do that. | 08:23 |
yuta-kazato | We assume that the target week for RC2 is week R-2 (until 3/10). | 08:24 |
yuta-kazato | Would Tacker team agree to the proposed RC2? or any comments? | 08:24 |
yuta-kazato | That's all from my side, thanks. | 08:24 |
yasufum | thanks | 08:25 |
w-juso | Thanks, I agree with you. Our patch is left yet.. | 08:26 |
ueha | Thank you for your suggestion. I agree to propose RC2. | 08:26 |
ueha | I have question that the target of RC2 written in https://etherpad.opendev.org/p/tacker-antelope-fixes-rc by yasufum is 16th March. Which is correct? | 08:26 |
yasufum | This date is just a candidate. | 08:27 |
yasufum | I think we should fix the deadline here. | 08:27 |
yuta-kazato | Thanks for agreements and comments. I agree with PTL to fix the deadline. | 08:28 |
yuta-kazato | for RC2. | 08:29 |
takahashi-tsc | 17th is Final RC deadline... I think RC2 deadline should be a little early. i.e. 10th seems better. | 08:30 |
ueha | 10th seems better> I agree, but I'm worried if we can review and fix the patch that ma-ooyama posted until 3/10. (today's 6th/7th topic) | 08:32 |
yasufum | that is the point | 08:33 |
yasufum | ma-ooyama: what do you think? | 08:34 |
ma-ooyama | Sorry for late submission about those. | 08:34 |
ma-ooyama | The 7th one is posted today, so I undestood the deadline is really short. | 08:35 |
ma-ooyama | I would appreciate it if you could review it but I understood it is hard for you.. | 08:36 |
yasufum | We cannot accept any patch after feature freeze without a fix for critical issue. | 08:38 |
yasufum | Is it a fix for such a problem? | 08:39 |
ma-ooyama | Sure. So I agree to set the deadline to 10th. | 08:40 |
ma-ooyama | No, it is not critical one. | 08:40 |
ma-ooyama | So please review the 6th one in this release. Is is OK? | 08:41 |
yasufum | I'll try, but cannot make any promise actually. | 08:43 |
ma-ooyama | Sure. Thanks. | 08:44 |
yasufum | Are you really agree to set the deadline to 10th? | 08:44 |
ma-ooyama | I want to if it is OK, but I cannot determine because it depends on your schedules. | 08:47 |
yasufum | I don't care if it's early next week, Monday or Tuesday hopefully. | 08:48 |
yasufum | ueha, takahashi-tsc: what do you think? | 08:49 |
takahashi-tsc | Hmm, 10th may be too strict... How about 14th? and we can discuss and decide whether remaining patches can/should be merged or not. | 08:50 |
takahashi-tsc | at this IRC call | 08:50 |
ueha | Considering that Zuul's CI is unstable a little and that there may be merge conflicts, I think it's good to put it next week... | 08:52 |
ueha | However, try to be able to merge within this week. | 08:53 |
ma-ooyama | Sorry... | 08:53 |
ma-ooyama | So I want to set the deadline to 14th and do our best to accomplish as much as possible. | 08:53 |
yuta-kazato | Thank you all for your consideration, cores and PTL. I agree to 14th as RC2 deadline. | 08:55 |
ueha | I agree too. | 08:55 |
yasufum | Thanks all for discussion. | 08:56 |
yuta-kazato | Thanks too. I will contribute to the review as much as possible. | 08:57 |
yasufum | thx | 08:57 |
yasufum | So, next topic is | 08:57 |
yasufum | #topic About "Support multiple conductors onboarding" | 08:57 |
ma-ooyama | Sure it is mine. | 08:58 |
yasufum | sure | 08:58 |
ma-ooyama | This topic is about https://review.opendev.org/c/openstack/tacker/+/874648 | 08:58 |
ma-ooyama | We added the "downloading" field to VnfPackage table. | 08:59 |
ma-ooyama | The detail is as written in the Etherpad. | 08:59 |
ma-ooyama | The field is not written in the Spec, so I would like to discuss whether it is acceptable to modify the spec and proceed to use the field. | 09:00 |
ma-ooyama | I would like to hear your opinions. | 09:00 |
yasufum | Although I'm not sure the diff of your change, | 09:02 |
yasufum | is it tiny change actually? | 09:02 |
ma-ooyama | I think so. The field is only used when onboarding is executed. | 09:03 |
yasufum | And the update of the spec is already included in your patch itself? | 09:04 |
ma-ooyama | Yes. I fixed the patch here. https://review.opendev.org/c/openstack/tacker-specs/+/875641 | 09:05 |
ma-ooyama | Put the link in the patch here. https://review.opendev.org/c/openstack/tacker/+/874648/comments/e98d5142_2d878a77 | 09:06 |
yasufum | OK. I understand it's just similar to a careless mistake, dropped a required field from spec | 09:07 |
ma-ooyama | Do you mean it is OK to add the field if the spec is modified? | 09:09 |
yasufum | if it's true. | 09:09 |
yasufum | But it's just my opinion. | 09:09 |
ma-ooyama | Thanks. | 09:09 |
yasufum | I don't really understand it's just a tiny mistake or not actually. | 09:09 |
yasufum | So, I'd like to hear any other comment from team. | 09:10 |
ueha | I think if an existing field is not available and it is really needed, it is no problem to add it. | 09:12 |
takahashi-tsc | I also think It is OK to accept... honestly it seems to be a little big impact because thisi is data model change. basically we have to be careful about such change. But... actually there seems be no problem. | 09:13 |
yasufum | thanks | 09:14 |
ma-ooyama | I understood it is hard to check the detail now. | 09:14 |
ma-ooyama | So I would appeciate it if you continue to review this on gerrit. | 09:14 |
yasufum | OK | 09:17 |
yasufum | The next item is the final topic. | 09:18 |
yasufum | ma-ooyama: Do you have any discussion point for the item today? | 09:18 |
ma-ooyama | Sure. This one is already discussed in the topic about deadline. | 09:19 |
yasufum | #topic About "Management Driver Improvement for Error Message" | 09:19 |
ma-ooyama | But I want to confirm again that | 09:20 |
ma-ooyama | this patch could be reviewed in RC2, right? or just "Support multiple conductors onboarding" only? | 09:21 |
yasufum | We've agreed to skip this one and will review as for bobcat, right? | 09:23 |
ma-ooyama | OK, understood. | 09:24 |
yasufum | because it's not a critical issue. | 09:24 |
yasufum | Any other discussion for the topic? | 09:25 |
ma-ooyama | So I don't have any discussion about this topic. Thanks. | 09:25 |
yasufum | OK. | 09:25 |
yasufum | Thanks, all topics done for today. | 09:25 |
yasufum | But I've found another patch appeared in the list of RC2 patches. | 09:26 |
yasufum | Who is the responsibility added on the etherpad for the patch? | 09:28 |
yasufum | #link https://review.opendev.org/c/openstack/tacker/+/850323 | 09:28 |
w-juso | I added patch in RC2 patches list. | 09:28 |
yasufum | Can you share what's happened or going on? | 09:29 |
yasufum | It already have two +2. | 09:30 |
w-juso | Yes. Regarding our patch, it seem like that workflow could not through gerrit. | 09:30 |
yasufum | But cannot pass the gate test. | 09:30 |
yasufum | yeah | 09:30 |
yasufum | Sorry, I've not noticed. | 09:31 |
yasufum | Did you find out the cause of the failure? | 09:31 |
w-juso | sorry, I'm not sure the cause in current. Can we make a recheck? | 09:33 |
yasufum | sure | 09:34 |
yasufum | Or, I think you should do that. | 09:34 |
yasufum | Anyway, we've already fixed RC1. | 09:35 |
w-juso | thank you, we'll check the recheck. | 09:35 |
yasufum | So, please propose another patch for stable branch as a backport. | 09:35 |
w-juso | ok | 09:36 |
yasufum | I think it's an occasional failurea and going to be merged by rechecking. | 09:38 |
yasufum | OK, any comment, or close this meeting? | 09:39 |
yasufum | good | 09:39 |
ueha | Sorry, I have one thing about the patch for 2023.1 release note | 09:39 |
ueha | https://review.opendev.org/c/openstack/tacker/+/876540 | 09:39 |
ueha | build-openstack-releasenotes job of this patch fails and I commentted to yasufum and tsc-takahashi. | 09:40 |
ueha | could you confirm about this. that's all. | 09:41 |
yasufum | hmm, I'll check it. | 09:41 |
yasufum | Thanks for your notice. | 09:41 |
takahashi-tsc | Hmm... | 09:41 |
ueha | For some reason, the previous release notes were also created as 2023.1 release notes... | 09:42 |
ueha | Other projects also seems to occur it, which can succeed or fail. | 09:43 |
yasufum | seems so | 09:44 |
yasufum | Anyway, let's close this meeting because it's so much time passed from the end of the time today. | 09:45 |
ueha | sure, let's discuss on gerrit patch. thank you. | 09:45 |
yasufum | Thanks for joining, bye. | 09:45 |
takahashi-tsc | bye | 09:45 |
ueha | thanks, bye | 09:45 |
w-juso | thanks, bye | 09:45 |
ma-ooyama | thanks bye | 09:45 |
yasufum | #endmeeting | 09:46 |
opendevmeet | Meeting ended Tue Mar 7 09:46:06 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:46 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2023/tacker.2023-03-07-08.02.html | 09:46 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2023/tacker.2023-03-07-08.02.txt | 09:46 |
opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2023/tacker.2023-03-07-08.02.log.html | 09:46 |
yuta-kazato | Thanks, bye. | 09:48 |
*** blarnath is now known as d34dh0r53 | 14:58 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!