#openstack-nova: nova
Meeting started by bauzas at 16:00:54 UTC
(full logs).
Meeting summary
-
- https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
(bauzas,
16:01:02)
- Bugs (stuck/critical) (bauzas, 16:03:48)
- No Critical bug (bauzas,
16:03:53)
- https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
38 new untriaged bugs (+1 since the last meeting) (bauzas,
16:03:56)
- Add yourself in the team bug roster if you want
to help https://etherpad.opendev.org/p/nova-bug-triage-roster
(bauzas,
16:05:40)
- Gate status (bauzas, 16:09:47)
- https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure
Nova gate bugs (bauzas,
16:09:52)
- https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly
Nova&Placement periodic jobs status (bauzas,
16:09:57)
- Please look at the gate failures and file a bug
report with the gate-failure tag. (bauzas,
16:10:04)
- https://zuul.openstack.org/build/13439683a24840f8b7a358c5e51e5c4e
(bauzas,
16:10:31)
- Release Planning (bauzas, 16:18:45)
- https://releases.openstack.org/caracal/schedule.html#nova
(bauzas,
16:18:49)
- Spec review day planned next Dec 5th
2023 (bauzas,
16:19:59)
- Caracal-2 (and spec freeze) milestone in 6
weeks (bauzas,
16:21:29)
- Review priorities (bauzas, 16:24:40)
- https://etherpad.opendev.org/p/nova-caracal-status
(bauzas,
16:24:45)
- https://bugs.launchpad.net/nova/+bug/1869804
and https://review.opendev.org/c/openstack/nova/+/877773 (bauzas,
16:25:10)
- Stable Branches (bauzas, 16:27:40)
- stable gates don't seem blocked (elodilles,
16:27:57)
- stable release patches still open for review:
https://review.opendev.org/q/project:openstack/releases+is:open+intopic:nova
(elodilles,
16:28:07)
- stable branch status / gate failures tracking
etherpad:
https://etherpad.opendev.org/p/nova-stable-branch-ci (elodilles,
16:30:49)
- vmwareapi 3rd-party CI efforts Highlights (bauzas, 16:36:11)
- Gerrit Event Stream connected to our CI (Argo)
with personal user (fwiesel,
16:36:53)
- CI user needs a name. According to naming
convention: SAP vmwareapi CI. Has risk of confusion, as SAP is not a
vendor of the technology. Our preference simply "SAP CI" or "SAP
tempest CI". (fwiesel,
16:38:48)
- Open discussion (bauzas, 16:47:03)
Meeting ended at 16:48:22 UTC
(full logs).
Action items
- (none)
People present (lines said)
- bauzas (78)
- elodilles (17)
- fwiesel (15)
- opendevmeet (5)
- sean-k-mooney (4)
- dansmith (4)
- gibi (3)
- auniyal6 (1)
- Uggla (1)
Generated by MeetBot 0.1.4.