Earlier  
Posted Nick Remark
#openstack-nova - 2024-06-03
14:27:04 opendevreview ribaudr proposed openstack/nova master: Add instance.share_attach notification https://review.opendev.org/c/openstack/nova/+/850501
14:27:06 opendevreview ribaudr proposed openstack/nova master: Add instance.share_attach_error notification https://review.opendev.org/c/openstack/nova/+/860282
14:27:06 opendevreview ribaudr proposed openstack/nova master: Add shares to InstancePayload https://review.opendev.org/c/openstack/nova/+/851029
14:27:08 opendevreview ribaudr proposed openstack/nova master: Add libvirt test to ensure metadata are working. https://review.opendev.org/c/openstack/nova/+/852086
14:27:08 opendevreview ribaudr proposed openstack/nova master: Add instance.share_detach_error notification https://review.opendev.org/c/openstack/nova/+/860283
14:27:10 opendevreview ribaudr proposed openstack/nova master: Docs about Manila shares API usage https://review.opendev.org/c/openstack/nova/+/871642
14:27:10 opendevreview ribaudr proposed openstack/nova master: Add virt/libvirt error test cases https://review.opendev.org/c/openstack/nova/+/852087
15:13:00 zigo https://paste.opendev.org/show/bOc8BpuH8DTiMSmtiQ5n/ <--- Anyone knows why eventlet monkey patching is broken for me?
15:17:54 zigo That's with Python 3.11 and Caracal, with eventlet 3.35.1 ...
15:27:59 zigo Looks like the issue is my backport to bookworm, somehow...
#openstack-nova - 2024-06-04
12:42:57 zigo I'm still getting the issue that Caracal doesn't like cpu_models = EPYC-Milan (nova-compute exists with "Unacceptable CPU info: CPU doesn't have compatibility"), even tough "virsh capabilities" shows that my host's CPU really is EPYC-Milan. Is the _check_cpu_compatibility somehow broken?!?
12:43:03 zigo How can I check what it does?
14:12:46 dansmith bauzas: do you want to +W this or should I? https://review.opendev.org/c/openstack/nova-specs/+/907654
14:13:13 bauzas dansmith: do this
14:13:39 dansmith bauzas: ?
14:16:54 sean-k-mooney bauzas: does that mean you will or that dan should
14:17:16 sean-k-mooney cause i was going to ask dansmith why he did not +w but then i saw this converstaion
14:17:59 dansmith I thought bauzas said several times he wanted to review that, so I held off the +W but I also didn't realize you had +2d yet
14:18:18 dansmith I was actually going to it to see the status and saw you had +2d
14:18:34 sean-k-mooney ack
14:18:43 dansmith but if bauzas isn't going to in short order, we should just send it I think
14:18:47 dansmith we're running out of time
14:19:23 sean-k-mooney i just the email update for your +2 and was wondering but was waiting for our downstream converation to come to an end before changing topic
14:20:39 sean-k-mooney anyway im cool leaving it to either of you to +w i was wondering if my +2 had been lost or not
14:23:45 bauzas ok, ok, I can try to give it a shot
14:28:01 dansmith bauzas: can you clarify what you're saying? _are_ you going to review that?
14:52:12 bauzas dansmith: sorry I had to take my daughter from school
14:52:17 bauzas if you want, I can review it indeed
14:52:41 dansmith bauzas: we're just trying to figure out if I should approve it, or of you *want* to review it first
14:55:08 bauzas dansmith: okay, so my point is that if you think all is good, you can approve it
14:56:26 dansmith done
15:04:30 opendevreview Merged openstack/nova-specs master: Re-propose specs for ephemeral encryption https://review.opendev.org/c/openstack/nova-specs/+/907654
16:00:41 opendevmeet The meeting name has been set to 'nova'
16:00:41 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:41 opendevmeet Meeting started Tue Jun 4 16:00:41 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:41 bauzas #startmeeting nova
16:00:45 bauzas hey folks
16:00:51 elodilles o/
16:00:55 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:01:03 bauzas should be a quick one hopefully
16:01:16 erlon \o
16:01:31 marlinc \o
16:01:43 kgube \o
16:01:45 auniyal o/
16:02:11 Luzi o/
16:02:26 marlinc I forgot to put my topic in the agenda, is that still oke?
16:02:38 bauzas shoot it in the agenda, sure
16:02:47 bauzas okay, let's start
16:02:54 bauzas #topic Bugs (stuck/critical)
16:03:02 bauzas #info No Critical bug
16:03:10 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:03:19 bauzas anything about buuugs ?
16:03:46 fwiesel \o
16:03:54 gibi o/
16:03:56 bauzas looks not
16:03:59 bauzas let's move on then
16:04:13 bauzas #topic Gate status
16:04:18 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:04:24 bauzas #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:04:32 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:04:38 bauzas (all greens, huzzah)
16:04:44 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:04:49 bauzas #info Please try to provide meaningful comment when you recheck
16:04:59 bauzas I haven't seen any important gate failure
16:05:09 bauzas and you ?
16:06:51 bauzas ok, np
16:06:57 bauzas #topic Release Planning
16:07:02 bauzas #link https://releases.openstack.org/dalmatian/schedule.html
16:07:08 bauzas as a reminder, nova deadlines are ^
16:07:15 bauzas #info Dalmatian-2 in 4 weeks
16:07:18 bauzas tick-tock
16:07:37 bauzas nothing planned as a review day until milestone-2 where we will have a spec review day
16:07:52 bauzas anything else about our schedule ?
16:07:57 erlon Is there a freeze day for bug fixes?
16:08:46 erlon I only see a freeze for specs
16:09:11 erlon ah, I see now, seems common to all projects
16:09:14 bauzas we can merge bugfixes until RC1
16:09:50 bauzas after RC1, we then branch master for Dalmatian
16:10:04 erlon ok, so, what kind of changes are accepted after RC1?
16:10:11 bauzas then, in between RC1 and GA, we can't merge any bugfix, ony regression fixes
16:10:24 erlon hmm, ok, makes sense
16:10:33 bauzas but we can still merge bugfixes in master
16:10:47 erlon Right, that will be available for the next release
16:10:54 bauzas since master will then be E (and no longer D) after RC1
16:11:17 bauzas so basically, we can merge any bugfixes anytime
16:11:22 bauzas for master
16:11:57 sean-k-mooney the only soft freeze is really betwee Feature freeze and RC1
16:12:02 bauzas but if you want your fix to be on a specific release, then either before RC1 or after GA by backporting it
16:12:14 sean-k-mooney we can merge a bugfix during that period but prefer to limit them ot regressions
16:12:18 erlon right
16:12:20 bauzas sean-k-mooney: not for bugfixes
16:12:45 bauzas anyway, I think you have your answer
16:12:50 bauzas can we move ?
16:13:03 bauzas #topic Review priorities
16:13:06 sean-k-mooney bauzas: we have prevsiously ased reviews not to merge bugfixes for bugs not intoduced in the current release in that period. but yes we can move on
16:13:14 bauzas #link https://etherpad.opendev.org/p/nova-dalmatian-status
16:13:24 bauzas nothing to say but please look at it ^
16:13:31 bauzas #topic Stable Branches
16:13:33 erlon I have a request here
16:13:46 erlon for Review priorities

Earlier   Later