16:00:21 #startmeeting nova 16:00:22 Meeting started Thu Apr 29 16:00:21 2021 UTC and is due to finish in 60 minutes. The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:25 The meeting name has been set to 'nova' 16:00:30 o/ 16:00:43 o/ 16:01:38 \o 16:02:01 \o 16:02:29 #topic Bugs (stuck/critical) 16:02:33 no critical bug 16:02:38 #link 27 new untriaged bugs (+9 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16:02:59 this is a morning data, after that we pushed down the backlog to 19 16:03:32 thank you all for the triages 16:03:47 is there any specific bug we need to talk about? 16:04:26 #topic Gate status 16:04:46 we have just merged the grenade zuulv3 change 16:04:57 that should make the nova grenade job green again 16:05:09 #link https://review.opendev.org/c/openstack/nova/+/778885 16:05:10 AFAIK the other gate issues in devstack have also been resolved 16:05:20 on same note, we are trying to drop the bionic support from devstack master 16:05:46 with nova greande job moving to zuulv3 we do not have any other pending bionic job 16:05:51 \o/ 16:05:53 no I don't think so 16:05:56 https://review.opendev.org/c/openstack/devstack/+/788754 16:06:00 we removed the base dsvm job as well 16:06:08 o/ 16:06:10 i will add testing patch too in case 16:06:17 lyarwood: +1 16:07:00 any other gate issues we need to discuss? 16:09:08 we disucssed that we will look at the periodic job results from placement at this point on the meeting but I don't think we have the periodic jobs in place yetr 16:10:06 I will ping sean-k-mooney about it 16:10:20 #topic Release Planning 16:10:25 The next release is in October. Nova specific schedule is on the wiki #link https://wiki.openstack.org/wiki/Nova/Xena_Release_Schedule 16:10:30 any comment about the schedule? 16:12:07 #topic PTG planning 16:12:11 Any feedback from last week, from the PTG? 16:13:32 #topic Stable Branches 16:13:39 copying elod's summary... 16:13:44 stable branch gates seem to be OK 16:13:48 train-em transition will happen within 2 weeks (2021-05-12) 16:13:52 final train release before the transition should be prepared as soon as possible (maybe around middle of next week?) 16:13:58 we should be careful what to merge before the final release, to avoid broken release that cannot be fixed, as there won't be any more train releases 16:14:02 on the other hand, if something should be merged, to be part of the final train release, then let us know -- e.g. in the etherpad: https://etherpad.opendev.org/p/nova-stable-train-em 16:14:06 EOM 16:14:13 any comment? 16:14:26 not from me 16:14:33 me too 16:14:43 and I think together with train we can release ussuri, victoria and wallaby maybe 16:14:45 about this #link https://review.opendev.org/c/openstack/placement/+/787526/2 16:15:18 It need one more +2 16:15:59 lyarwood: you have stable core rights on placment too right can you take a look 16:16:03 gmann: I can have a look after the meeting 16:16:05 its pretty simple 16:16:09 thanks 16:16:11 or elod :) 16:16:16 :) 16:17:08 anything else? 16:17:28 nothing from me 16:17:51 #topic Sub/related team Highlights 16:17:55 Libvirt (bauzas) 16:18:00 nothing to report, sir, just back from the PTG with no issues discovered, AFAICT. 16:18:24 thanks 16:18:29 #topic Open discussion 16:18:35 we have one on the agenda 16:18:43 (sean)review priorities https://review.opendev.org/c/openstack/project-config/+/787523 16:18:47 any objections to following gibis suggestion and making the range 0,+1 instead of -1..+2 16:18:56 thanks sean-k-mooney for proposing the config change 16:19:08 no worries 16:19:32 I have left a couple of comments on the review including the range question 16:19:39 sorry had to go afk, I can look at the placement change. 16:19:41 would be nice to get more opinion form the other cores 16:20:36 i was planning to update it this evening to make the range change but then im off until tuesday so if there are any other change requeted i can do them then 16:20:55 gibi: sean-k-mooney i agree, 0, 1 will serve the purpose. 16:21:03 0 and 1 worksforme 16:21:24 cool i did have one question actully 16:21:26 please check the patch I have other process related comments on it 16:21:41 many times in devstack or other repo I get confused with Review priority +2 with core vote +2 :) 16:21:56 for the stable branch shoudl the normal core team be abel to set it on the stable branches or jsut stable cores as i have it now 16:22:19 for me it is OK to have it only for the stable cores on stable branches 16:23:00 ok i was just wondering if it woudl be useful to allow the core team to flag that its important to merge on stable 16:23:00 +1 16:23:04 yup agreed 16:23:22 I think there's enough overlap at the moment that we shouldn't need to signal between the two 16:23:29 cool 16:23:53 in that cae read gibis comments on the patch and ill update it this evenign or tuesday when im back 16:24:03 cool 16:24:23 and I will propose a doc patch with the process to the nova repo 16:24:29 all good 16:24:50 any other topic for today? 16:24:53 and I'm OK with +0/+1 instead of -1/+1 16:26:39 OK, if nothing else for today 16:26:43 then thanks for joining 16:26:53 \o 16:26:58 o/ 16:27:00 #endmeeting