Earlier  
Posted Nick Remark
#openstack-nova - 2023-11-21
16:04:31 bauzas #info bug baton is bauzas
16:04:37 bauzas moving on
16:04:40 bauzas #topic Gate status
16:04:45 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:04:52 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:04:59 bauzas we had a fun gate blocker this week
16:05:31 sean-k-mooney the tooz thing?
16:05:31 bauzas #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/L72QU3SR2VFVYOFXVYH74V7HGMQ3YJRU/
16:05:39 bauzas yeah
16:05:55 sean-k-mooney you know we also use tooz in the ironic virt driver
16:06:00 bauzas anyway, we skipped the oslo tooz release
16:06:12 sean-k-mooney so its not just used by cinder
16:06:29 bauzas so now the tooz community needs to discuss how to support both etcd versions*
16:06:47 bauzas sean-k-mooney: sure but the gate was failing due to the cinder API issue
16:07:05 sean-k-mooney they could for now just swap to using hte memcached drier instead of ectd
16:07:07 sean-k-mooney in the gate
16:07:29 bauzas it's no longer a nova problem :)
16:07:42 sean-k-mooney :)
16:07:43 bauzas anyway
16:08:17 bauzas fwiw, now we have back a nova-emulation job issue https://zuul.openstack.org/builds?job_name=nova-emulation&project=openstack/nova
16:08:23 bauzas chateaulav: around ?
16:08:55 bauzas oh wait
16:08:59 bauzas this is not against master
16:10:14 sean-k-mooney ya so the emulation job i think is running on one of the stable branches
16:10:17 bauzas anyway, we'll see how this goes next week
16:10:20 sean-k-mooney which it should not be
16:10:58 bauzas sean-k-mooney: well, it's checking for yoga
16:11:04 sean-k-mooney its in check on yoga but it should only be in perodic-weekly
16:11:14 bauzas so probably in the next month, shouldn't be a problem :p
16:11:17 sean-k-mooney right we just forgot to move it on that branch
16:11:31 sean-k-mooney sure
16:11:37 bauzas we'll see
16:11:39 bauzas moving on
16:12:04 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:12:06 bauzas #topic Release Planning
16:12:12 bauzas #link https://releases.openstack.org/caracal/schedule.html
16:12:16 bauzas #info Nova deadlines currently on review https://review.opendev.org/c/openstack/releases/+/877094
16:12:34 bauzas I just hope the release cores will accept it quickly
16:12:54 sean-k-mooney its alredy merged
16:13:12 bauzas wow
16:13:16 bauzas haven't seen it
16:13:18 sean-k-mooney was that the right link
16:13:22 sean-k-mooney that was for bobcat
16:13:28 bauzas doh
16:13:33 bauzas #undo
16:13:33 opendevmeet Removing item from minutes: #info Nova deadlines currently on review https://review.opendev.org/c/openstack/releases/+/877094
16:13:43 sean-k-mooney https://review.opendev.org/c/openstack/releases/+/901547
16:14:10 bauzas #info Nova deadlines currently on review https://review.opendev.org/c/openstack/releases/+/901547
16:14:18 sean-k-mooney it has a -1 for elod specfreeze is wrong
16:14:19 bauzas okay, just saw elodilles's question
16:14:26 elodilles o:)
16:14:29 bauzas I'll look at it
16:14:42 sean-k-mooney elodilles:++ sorry that should read from not for
16:14:51 bauzas and yeah you're right
16:15:11 bauzas elodilles: indeed was wrong, should be milestone-2 for spec freeze, my bad :)
16:15:20 elodilles np :)
16:15:28 bauzas I'll upload a new rev
16:15:39 elodilles thx
16:16:13 bauzas #info Caracal-2 (and spec freeze) milestone in 7 weeks
16:16:41 bauzas as a reminder, we'll have another spec review day
16:17:13 bauzas now, I have a question
16:17:41 bauzas we said necxt week that we could add a caracal-1 tag for nova
16:17:53 bauzas but then I looked at all the releases we did from yoga
16:18:01 bauzas and none of them have any milestone tag
16:18:10 bauzas hence my question
16:18:16 bauzas should we create a specific milestone for Nova and Placement?
16:18:19 bauzas I don't think so
16:18:21 sean-k-mooney we are not required to create them. we are just required to have 1 rlease before the final release
16:18:29 sean-k-mooney so the RC-1 release covers that
16:18:31 bauzas this is rc1
16:18:36 bauzas yeah
16:18:58 sean-k-mooney i dont personlly think milestone release make sense for nova
16:18:58 bauzas and I very quickly looked at cinder, they don't add a milestone too
16:19:03 sean-k-mooney or non lib projects
16:19:07 bauzas yup
16:19:11 elodilles no need for Caracal-1 (.b01) release (which is not rc1)
16:19:23 elodilles for nova & placement
16:19:27 elodilles imo
16:19:34 bauzas the only usecase would be for operators if they want to test milestones
16:19:52 elodilles (it's just a possibility, but we don't need)
16:19:54 bauzas but we haven't had any operators doing this from a long time
16:19:59 bauzas okay
16:20:01 sean-k-mooney they could just deploy a commit at that point
16:20:21 sean-k-mooney googing though the release process for that has very little return
16:20:36 sean-k-mooney we do it for libs since we do not install libs form git as the default
16:20:40 bauzas #action bauzas to not provide a caracal-1 tag actually (compared to what we said on the previous weekly meeting)
16:20:42 sean-k-mooney unlike service projects which we do
16:20:49 bauzas I'm fine
16:21:00 bauzas I just wanted to remove the action item that we agreed last week
16:21:01 elodilles +1
16:21:20 bauzas I don't know how many people read our meeting minutes but... :)
16:21:33 bauzas anyway, moving on
16:21:46 bauzas #topic Review priorities
16:21:51 bauzas #link https://etherpad.opendev.org/p/nova-caracal-status
16:21:53 bauzas hehe
16:22:21 bauzas so, folks who want to add some bugfixes can now add them in ^
16:22:41 bauzas we have a specific section
16:22:55 bauzas and cores, please look at this etherpad in order to know what to review
16:23:05 gibi aye sir :)
16:23:34 bauzas nay, I'm not a sir :)

Earlier   Later