Earlier  
Posted Nick Remark
#openstack-nova - 2022-07-05
16:15:09 bauzas but I don't want to discuss one of them by now
16:15:22 bauzas #link https://storyboard.openstack.org/#!/project/openstack/placement 27 open stories (+0 since the last meeting) in Storyboard for Placement
16:15:28 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:15:48 bauzas so, the next folk in the roster is artom
16:16:16 bauzas artom: can you be the next bug baton owner, or anyone else ?
16:17:46 bauzas mmm, looks like artom isn't around
16:17:59 sean-k-mooney that means we can give them more work to do right
16:18:04 gibi right :)
16:18:17 bauzas hah
16:18:18 gibi he had on PTO last week so he is well prepared ;)
16:18:28 bauzas I triaged for two weeks
16:18:33 bauzas I paid my duty :D
16:18:59 elodilles i'm not that efficient as others, and probably will be afk 1 day, but can try to have the baton
16:19:03 bauzas (well, actually I triaged every Yoga week, until gibi told we should have a triage team :) )
16:19:24 gibi I think we can convice artom to take it :)
16:19:35 elodilles gibi: that also works for me :)
16:19:36 gibi he is just probably busy with someting else right now
16:19:40 bauzas let me gently force artom to get the baton :)
16:19:50 bauzas not in a passive aggressive way
16:19:51 gibi lets but it on artom tentatively and we can re-think if he rejects it
16:19:57 bauzas but rather talking with him in French
16:20:38 bauzas cool
16:20:46 bauzas #info Next bug baton is passed to artom
16:20:53 bauzas moving on
16:20:55 bauzas #topic Gate status
16:21:00 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:21:17 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
16:21:21 bauzas #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs
16:21:28 bauzas both weekly jobs run fine
16:22:03 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:22:08 bauzas #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures
16:22:14 bauzas oh, I forgot to add in the agenda
16:22:18 bauzas we have numbers
16:22:39 bauzas #link https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029363.html
16:23:02 bauzas #undo
16:23:02 opendevmeet Removing item from minutes: #link https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029363.html
16:23:06 sean-k-mooney ya nova was not too bad but there are still some
16:23:27 bauzas #link https://lists.openstack.org/pipermail/openstack-discuss/2022-June/029342.html
16:24:04 bauzas #info 57.75% of rechecks were without a reason, please refrain this wrong behaviour
16:24:12 dansmith ++
16:24:52 bauzas moving on
16:24:56 bauzas #topic Release Planning
16:25:00 bauzas #link https://releases.openstack.org/zed/schedule.html
16:25:05 bauzas #info Zed-2 is in 1.5 weeks
16:25:09 bauzas #info Spec review day today
16:25:18 bauzas well, this was actually a quiet review day
16:25:27 bauzas only 3 specs are currently open to reviews
16:25:36 dansmith I spent a lot of time on the ironic one,
16:25:43 bauzas dansmith: appreciated a lot
16:25:51 dansmith although I'm not sure I'd even call it a spec
16:25:52 gibi yeah the ironic one is the hard piece
16:26:05 bauzas dansmith: I tried to look at it and then I had to stop b/c I had to do bug triage
16:26:21 bauzas dansmith: we basically agreed on the fact this isn't purely a spec
16:26:27 dansmith it's really just brainstorming, so has nothing to do with the spec deadline, IMHO
16:26:38 bauzas it's a document trying to identify all the corner cases about the proposed implementation
16:26:42 gibi depending on an agreed solution we might need a real spec :)
16:26:45 bauzas dansmith: agreed
16:26:54 bauzas on the existing document
16:26:57 gibi but agreed to brainstorm first
16:27:06 bauzas I don't feel it's constrained by the spec approval freeze
16:27:14 sean-k-mooney yep i have not looked at it in a while but its on my todo list at the end
16:27:16 sean-k-mooney after the rest
16:27:29 bauzas but yeah, as gibi said, depending on the consensus we may achieve, this would require some design stage. Or not.
16:27:43 dansmith anything we do would need a spec I'm quite sure,
16:28:03 dansmith I'm just saying, there's no reason to spend time reviewing it instead of other specs before the deadline
16:28:06 bauzas I'll make clear on the gerrit change this one isn't impacted by our deadlines
16:28:15 dansmith I didn't really realize that until it was too late for me, but SAVE YOURSELVES
16:28:16 dansmith :P
16:28:27 bauzas dansmith: honestly, besides this one which is hairy, we only have two opens
16:28:32 bauzas one is about to be merged
16:28:33 dansmith I threw a -1 on it for visibility since all the others were just +0 comments
16:28:42 bauzas and the other one potentially misses resources to work one
16:28:44 bauzas on*
16:28:46 dansmith cool
16:29:05 bauzas so I just feel we can spend brain cycles on the rebalance issue
16:29:11 dansmith ack
16:29:14 sean-k-mooney since it was a braninstromign doc i just didn nto +/- since it did not have any singel proposal
16:29:32 bauzas sean-k-mooney: I'll clarify the purpose of this document in a gerrit comment
16:29:34 sean-k-mooney but yes ack on the -1
16:30:18 dansmith sean-k-mooney: yeah and that's fair, but someone could stumble in thinking it was needing review before the deadline with no other signaling :D
16:30:39 bauzas I'll send the signal
16:30:45 dansmith ++
16:30:56 bauzas ideally, I asked CERN folks to jab into it
16:31:05 bauzas but, this is just an ask
16:31:26 bauzas they're impacted by the rebalancing issue as they don't use the ironic feature
16:31:40 sean-k-mooney so in terms of other specs
16:31:42 bauzas so I'd also like to understand whether we could have a mitigation
16:31:54 sean-k-mooney im expecting artom to update theres later this week
16:32:05 sean-k-mooney and ill try and updte teh power managment one
16:32:11 sean-k-mooney but im aware both are late
16:32:13 sean-k-mooney and may slip
16:32:23 bauzas sean-k-mooney: I left a comment on artom's spec, there could be effort to spend on the EC2 compatible API
16:32:44 sean-k-mooney well ok but im not sure we care about ec2 compat
16:33:01 bauzas sean-k-mooney: maybe, but the spec was saying we were given ec2 compat for free
16:33:08 bauzas which isn't true
16:33:13 sean-k-mooney ack
16:33:39 bauzas for the power management spec, you still have one week to push it
16:33:57 bauzas given we lack of open specs, I could be able to quickly jump into it
16:33:58 sean-k-mooney main issue is reloading context i have not worked on it since febuary
16:34:02 bauzas me too

Earlier   Later