16:00:01 #startmeeting nova 16:00:01 Meeting started Tue Mar 1 16:00:01 2022 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:01 The meeting name has been set to 'nova' 16:00:11 hello everyone 16:00:18 hey 16:00:22 #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 16:00:47 o/ 16:00:49 o/ 16:01:08 \o 16:01:47 ok let's start, people will join 16:01:55 #topic Bugs (stuck/critical) 16:01:59 #info No Critical bug 16:02:04 #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 28 new untriaged bugs (+1 since the last meeting) 16:02:08 #help Nova bug triage help is appreciated https://wiki.openstack.org/wiki/Nova/BugTriage 16:02:12 #link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (-1 since the last meeting) in Storyboard for Placement 16:02:28 we're entering the RC period, which is always a good time for looking at open bugs :) 16:02:37 * bauzas will do this week 16:02:50 any bug people want to discuss ? 16:03:15 (I'll explain the difference between RC1 and other RCs later in the meeting) 16:03:47 looks not 16:03:54 I take your silence as a no :) 16:03:59 #topic Gate status 16:04:03 #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:04:07 #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status 16:04:11 #info Please look at the gate failures and file a bug report with the gate-failure tag. 16:04:36 nothing to mention here, we don't have new failure bugs AFAICS 16:05:00 again, any gate issue people want to discuss ? 16:05:33 - 16:06:16 nope 16:06:59 k 16:07:09 next huge topic 16:07:12 #topic Release Planning 16:07:17 #link https://releases.openstack.org/yoga/schedule.html#y-ff FeatureFreeze happened last Thursday Feb 24th 16:07:20 #link https://etherpad.opendev.org/p/nova-yoga-blueprint-status Etherpad for blueprints tracking 16:07:27 I updated it 16:07:39 we have a few follow-ups for impemented blueprints 16:07:51 but they will be merged in the next days 16:08:14 none of the changes are about providing a feature, they are just nits or CI changes 16:08:46 that's why I said "Implemented" to all the merged blueprints 16:08:52 #link https://blueprints.launchpad.net/nova/yoga 16:08:56 #info 12 Nova blueprints and 1 Placement story successfully merged on Yoga, 12 were deferred to Zed 16:09:36 I'll remove the series goal for the 12 deferred ones 16:09:45 but at RC1 16:10:02 12 +1 is good number I think 16:10:14 thanks btw. for folks that helped to review 16:10:32 gmann: indeed, about 50% of the accepted blueprints 16:10:49 and 50% of the deferred ones were because nobody was working on them 16:11:14 again, thanks folks 16:11:49 and also, thanks contributors that continued to discuss with us and provided new revisions when it was needed :) 16:12:03 ++ 16:12:14 I take it as a good cycle 16:12:39 it was a good one 16:12:40 hopefully the better we are, the larger contributors we'll have :) 16:13:17 anyway, now, yoga-3 is released 16:13:27 now, it's time to work on RC1 16:13:40 #link https://releases.openstack.org/yoga/schedule.html#y-rc1 RC1 is now due on March 10th 16:13:50 which is in less than 2 weeks 16:14:15 for tracking, I created the usual etherpad 16:14:20 #link https://etherpad.opendev.org/p/nova-yoga-rc-potential Etherpad for RC tracking 16:14:26 please open it 16:15:01 you'll see that we already merged the RPC and the API version changes 16:15:21 now, we need someone to work on the reno prelude 16:15:41 who wants to contribute for it ? ^ 16:16:13 fwiw, this prelude should be quite the cycle highlights https://review.opendev.org/c/openstack/releases/+/831241 16:16:22 if nobody wants to do it, I can work on it 16:16:39 that's not like I did it for most of the older cycles: p 16:17:06 ok, I take it as "yes, please do" :p 16:17:09 bauzas: do we have the standard bug tag created yet for rc potential 16:17:22 sean-k-mooney: indeed, that was the next iteam 16:17:25 item* 16:17:32 ack 16:17:39 we now have in the etherpad https://bugs.launchpad.net/nova/+bugs?field.tag=yoga-rc-potential 16:18:28 #info please mark any important bug as a RC potential one by adding yoga-rc-potential tag to your bug report 16:18:38 for the moment, we have none of them 16:19:02 for RC1, any bug can be accepted 16:19:10 Merged openstack/nova master: Lightos driver release note https://review.opendev.org/c/openstack/nova/+/830817 16:19:22 after RC1, we'll only accept bugs that fix a regression 16:19:41 i have one we may want to consider 16:19:46 sean-k-mooney: sure 16:19:57 we can talk about it in open discuss if you prefer 16:20:58 or now https://review.opendev.org/c/openstack/nova/+/830966 bacially we disable eventlet monkey patching of dns 16:21:17 because back on python 2.6/centos 6 it broke ipv6 16:21:29 we can discuss this now 16:21:36 but apparently that can cause the api to hang since its a blocking call 16:21:54 so im wondering do we want to revert the workaround 16:22:03 OK, please mark the bug report as RC potential then 16:22:04 if so i can file an upstream bug and refrence the downstream one 16:22:17 yes, please 16:22:44 ok ill do it after the meeting and we can decied later if we want to make that change now or next cycle and backport 16:22:46 RC1 is always a good time for discussing about the bugs we know but we never have time to look at 16:23:17 how risky it is? 16:23:20 ya https://bugs.launchpad.net/nova/+bug/1164822 is what the orginal patch was trying to fix 16:23:33 (I'd personnally be in favor of a larger period in time for caring about bugs, but I also understand how quick it is to merge blueprints by 2.5 months) 16:23:35 gibi: well you can get the same effect by exporting a env var 16:23:44 so not really imo 16:23:59 then I'm OK 16:24:07 sicne installer coudl always get the same behavior 16:24:08 with this bug being merged before RC1 16:24:11 let's mark it for now, and we'll revisit it off-topic during the week 16:24:17 ack 16:24:21 ack 16:24:29 I'll ping people on IRC that mark bugs as potential 16:24:37 to see how important this is 16:24:45 please stay close to your IRC client :) 16:25:49 ok, I guess we're done with this topic 16:26:20 I haven't mentioned the clients release but the patch is going 16:26:35 the client shoudl already be done 16:26:45 the final release of osc-placment and nova client is already done 16:27:29 this is there https://review.opendev.org/c/openstack/releases/+/831293 16:28:02 that not doign a release 16:28:07 we have a osc-placement patch for supporting the latest API microversion for any-traits, but gibi agreed on it not being needed for Yoga 16:28:12 it just creating the branches 16:28:19 bauzas: yepp 16:28:35 as sean-k-mooney says :] 16:28:40 oh yeah 16:28:43 correct 16:28:49 but ya we shoudl also do that :) 16:28:57 i.e. create the branches 16:28:58 but we're branching on already delivered versions, right? 16:29:08 yes 16:29:10 releases were out last week 16:29:11 yes 16:29:13 which we released a few days ago 16:29:19 on friday 16:29:21 so we're good 16:29:24 yes 16:29:33 we're just branching, but releƩases are already gone 16:29:47 yepp :) 16:30:03 yep elodilles pingged me and you on friday and i approved them a release leasion 16:30:12 sicne you were busy 16:30:22 great thanks then 16:30:29 anyway, I guess we can move on then 16:30:47 sean-k-mooney: appreciated, the beauty of delegating :) 16:31:01 :) 16:31:12 ok, moving on, time flies 16:31:19 #topic Review priorities 16:31:24 #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+label:Review-Priority%252B1 16:31:31 I only marked the osc-placement patch 16:31:46 I'd hold my vote until we branch 16:32:19 but given nobody +2d/+Wd we're safe 16:33:13 anything to add ? 16:34:08 - 16:34:22 #topic Stable Branches 16:34:27 elodilles: floor is yours 16:34:32 #info queens and pike branches are blocked 16:34:40 #info WA patch for stable/wallaby gate stability needs 2nd +2: https://review.opendev.org/830656 16:34:51 maybe this can have a prio ^^^ o:) 16:35:15 because wallaby patches cannot really merge due to high failure rate 16:35:25 #info stable/queens gate fix waiting for 2nd +2: https://review.opendev.org/830327 (needs to be backported to pike as well) 16:35:38 we haven't done stable releases for a long time, release patches now proposed: https://review.opendev.org/q/project:openstack/releases+intopic:nova+is:open 16:35:54 I've seen them 16:36:10 I added them in the RC etherpad for making sure we don't forget them 16:36:11 maybe this is a good time to release them, but let me know if we need to wait 16:36:25 bauzas: ++ 16:36:49 I don't see any reason to hold a stable release but I could be wrong, I need to look at the open patchs 16:36:54 patches* even 16:37:26 but yeah, we need other cores for the stable branches fixes :) 16:37:32 just sayin' 16:37:50 * gibi still not have the power over stable :) 16:37:51 Dan Smith proposed openstack/nova master: Add support for volume backed server rebuild https://review.opendev.org/c/openstack/nova/+/820368 16:37:52 Dan Smith proposed openstack/nova master: Add conductor RPC interface for rebuild https://review.opendev.org/c/openstack/nova/+/831219 16:37:52 Dan Smith proposed openstack/nova master: Add API support for rebuilding BFV instances https://review.opendev.org/c/openstack/nova/+/830883 16:37:54 whoami-rajat: ^ 16:38:21 if bug fixes are landing during FF and final RC and we backport some of them then we can do another round of stable release 16:38:36 i think ^^^ 16:38:37 dansmith: dude, we're in meeting, shhhttttt :p 16:38:49 gibi: oh, that. 16:38:53 gibi: could be fixable 16:38:56 ;) 16:39:10 :) 16:39:12 * bauzas should write a new thread then 16:39:14 bauzas: apologies 16:39:31 dansmith: heh no worries you're not the first and you won't be the last 16:39:49 that's the drawback of in-channel meetings per se 16:39:55 anyway 16:39:59 nothing on stable, folks ? 16:40:27 guess not 16:40:32 #topic Open discussion 16:40:39 this topic has nothing on the agenda 16:40:50 any stuff someone wants to raise ? 16:41:00 or shall I close it ? 16:41:04 i have one thing for us to reflect on. os-vif is pretty stable at this point i wonder if it makes sense to move to release independet 16:41:32 sean-k-mooney: interesting thoughts but I wonder if that would be more suitable at a PTG timing 16:41:43 I'd be interested in hearing thoughts from the neutron team 16:41:45 we dont need to make any decission now ya we can discuss at ptg 16:42:15 tbc, release-independent doesn't prevent you to release at milestones 16:42:23 correct 16:42:25 it's just, you're free to do as you want 16:42:32 it just remove the requiremetn to have at least one release a cycle 16:42:41 sec 16:42:46 verifying the requirements 16:43:00 we tend to have enough to do 1 release a cycle but typically dont have a need to do more hten one 16:43:10 which we can do with the current model too 16:43:12 https://releases.openstack.org/reference/release_models.html#independent 16:43:20 the definition ^^^ 16:43:21 * bauzas reads https://releases.openstack.org/reference/release_models.html 16:43:27 damn, burned 16:43:34 :] 16:43:59 we currently use cycle-with-intermediary which works fine 16:44:20 well, then let's discuss this at the PTG 16:44:24 but most of the changes tend to be paper work 16:44:26 ack 16:44:39 enforcing a release per cycle is something a bit loud, but this could be necessary 16:45:04 releasing the enforcement doesn't sound bad at a first glance, but I wonder the implications 16:45:16 one significant thing is that os-vif won't have stable branches, 16:45:26 but i think not so much backports arrives there 16:45:34 elodilles: ya but we dont really do backports often 16:45:46 sean-k-mooney: ++ 16:45:53 we do bug i can proably count them on two hands for the last 2-3 releases 16:45:55 but then we loose the possibility of doing them :) 16:46:02 yep 16:46:07 lets talk about it later 16:46:10 yup 16:46:13 just wanted people to think about it 16:46:16 thanks 16:46:25 any other topic ? 16:46:54 sean-k-mooney: please put it somewhere in your brain until the ptg etherpad is created, I don't want to miss this conversation at the PTG 16:47:28 that said, if nobody has any items... 16:47:37 thanks all 16:47:42 #endmeeting