Weekly Nova team meeting

Regular MEETING TIME: Tuesdays 16:00 UTC (#openstack-nova on OFTC)

This meeting is a weekly gathering of developers working on OpenStack Compute (Nova). We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.

Project Heartbeat

This information will be updated weekly but not mentioned in the meeting unless specifically called out on the agenda.

#topic Release News
- #link Nova 2023.2 Bobcat schedule https://releases.openstack.org/bobcat/schedule.html
- #link Nova 2023.1 Antelope schedule https://releases.openstack.org/antelope/schedule.html

#topic Stable branch status

#topic Bugs (stuck/critical)
- #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags
- #help need help with bug triage

#topic Gate status
- #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
- #link 3rd party CI status (not so dead) http://ciwatch.mmedvede.net/project?project=nova

#topic Review status page
- #link http://status.openstack.org/reviews/#nova
- Count: 438 (+20); Top score: 2303 (+21) (last refresh was 09-03)
- #help Pick a patch near the top, shepherd it to closure

Agenda for next meeting

Next meetings scheduled for:

Apr 04 2023 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2023-04-03T16:00:00)
Apr 11 2023 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2023-04-11T16:00:00)
Apr 18 2023 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2023-04-18T16:00:00)
Apr 25 2023 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2023-04-25T16:00:00)

Where you see "?" feel free to just edit the wiki and add your item.

Here is the agenda for the next meeting:

#topic Bugs (stuck/critical)
- #info No Critical bug
- #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 13 new untriaged bugs (-5 since the last meeting)
- #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
- #info bug baton is being passed to melwitt

#topic Gate status
- #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
- #link https://etherpad.opendev.org/p/nova-ci-failures
- #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
- #info Please look at the gate failures and file a bug report with the gate-failure tag.
- #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures

#topic Release Planning
- #link https://releases.openstack.org/bobcat/schedule.html
- #info Nova deadlines are set in the above schedule
- #info Bobcat-1 is in 3 weeks

#topic Review priorities
- #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2)
- #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review

#topic Stable Branches
- #info final Xena release (24.2.1) is out - ready to transition stable/xena to EM
- #info stable gates are not blocked, but sometimes patches need many rechecks
- #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
- #info Please review these backport patches for zed and yoga release
- #link https://etherpad.opendev.org/p/release-liaison-PatchesToReview

#topic Sub/related team Highlights
- #info No subteam left

#topic Open discussion
- (ykarel) Allow to add tb-cache size libvirt option for qemu, context https://bugs.launchpad.net/nova/+bug/1949606
  - qemu-5.0.0(included in ubuntu jammy) update default tb cache size to 1 GiB(from 32 MiB) for system-emulated guest vms and with that each guest VM is using much more system memory(1 GB+ memory for guest), resulting into oom-kill issues when creating multiple guest vms concurrently in neutron scenario jobs using ubuntu guest vms
  - should this be a specless RFE or can continue as a bug?
  - Default setting for this new option, unconfigured or set to defaults like 32MB or 128 MB etc?

Sub-teams

There are also some Nova subteam meetings. See Nova#Nova_subteams for details.

Previous meetings

All other meetings are here

Meetings/Nova

Contents

Weekly Nova team meeting

Project Heartbeat

Agenda for next meeting

Sub-teams

Previous meetings