Earlier  
Posted Nick Remark
#openstack-nova - 2024-02-13
14:32:58 sean-k-mooney both worked
14:34:00 sean-k-mooney im going to create a new note and continue testing but i started working at 5am my timea and its now 14:30 ish so im undesincedif im going to keep workign today and just not work friday or finish shortly
15:14:40 opendevreview Merged openstack/nova master: Augment the LibvirtLiveMigrateData object https://review.opendev.org/c/openstack/nova/+/904175
15:15:45 gibi Uggla: left feedback in the manial series
15:17:42 Uggla gibi thanks I'm gonna have a look.
15:42:08 wncslln hello nova o/, I have a environment with kolla and I have been a problem with nova and rabbitmq. In one of the tasks, it tries to ensure that rabbitmq user exists, but crashes and we not could reconfigure nova service :(
15:42:10 wncslln anyone can help?
15:44:08 wncslln i mispoken. I have been facing a problem*
16:00:15 opendevmeet The meeting name has been set to 'nova'
16:00:15 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:15 opendevmeet Meeting started Tue Feb 13 16:00:15 2024 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:15 bauzas #startmeeting nova
16:00:19 bauzas hey folks
16:00:35 auniyal o/
16:00:38 dansmith o/
16:00:49 bauzas sorry, those days I'm a bit off from the channel
16:01:03 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:01:05 elodilles o/
16:01:08 ratailor o/
16:01:13 bauzas let's start
16:01:17 bauzas people will arrive
16:01:23 bauzas #topic Bugs (stuck/critical)
16:01:27 bauzas #info No Critical bug
16:01:31 bauzas #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 59 new untriaged bugs (+3 since the last meeting)
16:01:36 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:01:40 bauzas #info bug baton is bauzas
16:01:41 gibi o/
16:01:48 bauzas (I forgot again to look at the bugs :( )
16:02:03 bauzas any bugs you would want to discuss ?
16:02:34 bauzas looks not, moving on
16:02:43 bauzas #topic Gate status
16:02:46 fwiesel \o
16:02:48 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:02:52 bauzas #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:02:56 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:03:00 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:03:34 bauzas so, we have some issue with the c9s job
16:03:40 bauzas but we know why :)
16:03:55 bauzas (some libvirt regression)
16:04:46 bauzas in the next week, the new libvirt release (that fixes the issue) would be in the c9s
16:05:14 bauzas (hopefully)
16:05:52 bauzas any CI failures you would want to discuss ?
16:07:54 bauzas looks not
16:08:01 bauzas moving on
16:08:17 bauzas #topic Release Planning
16:08:21 bauzas #link https://releases.openstack.org/caracal/schedule.html#nova
16:08:25 bauzas #info Caracal-3 (and feature freeze) milestone in 2 weeks
16:08:29 bauzas tick-tock
16:08:38 bauzas 2 weeks and a half, tbh
16:09:21 bauzas for me, given I was working on my own series for testing it, I'll eventually review by tomorrow
16:09:33 bauzas review *other* features, I mean
16:09:57 bauzas I was wanting to do this today, but I had another problem that I fixed
16:10:15 bauzas so, please look at your gerrit emails tomorrow :)=
16:10:21 bauzas #topic Review priorities
16:10:24 bauzas #link https://etherpad.opendev.org/p/nova-caracal-status
16:10:30 bauzas again, everything is there
16:10:46 bauzas nothing to say more about it
16:10:52 bauzas #topic Stable Branches
16:10:59 bauzas elodilles: heya
16:11:02 elodilles o/
16:11:09 elodilles #info stable/ussuri transitioned to End of Life
16:11:21 elodilles this i forgot to mention last week ^^^
16:11:34 bauzas \o/
16:11:35 elodilles #info unmaintained/yoga is open for patches
16:11:56 elodilles though gate might be still problematic, but at least generated patch has merged \o/
16:12:12 elodilles #info stable gates don't seem blocked, though deleted stable/yoga can cause problems (e.g. on grenade jobs)
16:12:51 elodilles this might be important for 2023.1 (skip level grenade) and zed (grenade) for the coming weeks ^^^
16:13:14 elodilles so probably the best is to follow things here:
16:13:18 elodilles #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:13:32 elodilles and maybe one more thing to mention:
16:13:49 elodilles now that we have unmaintained/yoga
16:14:20 elodilles so far only openstack-unmaintained-core have rights for nova's unmaintained/ branch
16:14:31 elodilles there are two option here
16:14:41 elodilles 1) add people to this group
16:14:55 elodilles 2) create a nova-unmaintained-core group
16:15:09 dansmith the goal is that most projects go with #1
16:15:11 elodilles and populate that one with interested people ^^^
16:15:26 bauzas I have no opinion
16:15:34 elodilles dansmith: yepp, true, though some project already started to create their own group
16:15:46 dansmith meaning "nova doesn't really maintain the unmaintained stuff, but community members that are interested in old versions do"
16:16:00 dansmith elodilles: right, but see the discussion in -tc right now.. that seems to be a misundersanding
16:16:02 elodilles anyway, this is just a heads up to the team to think about this
16:16:17 bauzas but in general, people wanting to "maintain" a project also wants to maintain cinder and neutron
16:16:18 gibi I don't want to maintain ussuri :)
16:16:20 elodilles dansmith: ACK
16:16:22 dansmith we're hoping/expecting most projects to effectively let those dry up and only get maintained if there are people around to care
16:16:47 dansmith bauzas: right, the idea is someone maintaining ussuri need to care about nova and neutron in that release, so let them
16:16:56 elodilles ACK, then we can keep things as it is then :)
16:17:01 bauzas tbh, after thinking a bit, I wouldn't want to have a specific group told 'nova-' something
16:17:05 dansmith that's certainly my preference
16:17:21 elodilles (note, i am member of openstack-unmaintained-core, so either way, i have rights to mess around there)
16:17:22 bauzas so no about 2) if the name is 'nova-unmaintained-group'
16:17:29 dansmith the idea is that the nova project gets to stop worrying about those old releases
16:17:42 dansmith if we create a nova- group, we kinda have to keep caring about it
16:17:45 bauzas yeah, that's why I don't want that group to be named 'nova'
16:17:52 bauzas dansmith: that's my point
16:17:56 dansmith yup
16:18:08 elodilles ACK
16:18:28 elodilles OK, that's it from my side then about stable :X
16:18:39 bauzas anyway, the unmaintained branch is no longer supported by nova

Earlier   Later