Revision as of 15:59, 19 July 2022

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 Yoga schedule https://releases.openstack.org/yoga/schedule.html

• #topic Stable branch status
  • #link stable/yoga: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/yoga
  • #link stable/xena: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/xena
  • #link stable/wallaby: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/wallaby
  • #link stable/victoria is EM

• #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:

• July 19 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-07-19T16:00:00)
• July 26 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-07-26T16:00:00)
• Aug 02 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-08-02T16:00:00)
• Aug 09 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-08-02T16: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://review.opendev.org/c/openstack/nova/+/849463 move the C9S job to both experimental and periodic-weekly
  • #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 10 new untriaged bugs (-1 since the last meeting)
  • #link https://storyboard.openstack.org/#!/project/openstack/placement 27 open stories (+0 since the last meeting) in Storyboard for Placement
  • #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
  • #info Next bug baton is passed to sean-k-mooney

• #topic Gate status
  • #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
  • #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
  • #link https://zuul.openstack.org/builds?job_name=tempest-integrated-compute-centos-9-stream&project=openstack%2Fnova&pipeline=periodic-weekly&skip=0 Centos 9 Stream periodic job status
  • #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs
  • #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/zed/schedule.html
  • #info Zed-2 was last week
  • #info Specs are no longer accepted

• #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
  • #link https://review.opendev.org/c/openstack/project-config/+/837595 Gerrit policy for Review-prio contributors flag. We need project-config cores to merge it.
  • #link https://docs.openstack.org/nova/latest/contributor/process.html#what-the-review-priority-label-in-gerrit-are-use-for Documentation we already have
  • #link https://review.opendev.org/c/openstack/nova-specs/+/816542 Spec for modifiable user_data was accepted / merged, but implementations are still pending final review / merge
    • #link https://review.opendev.org/c/openstack/nova/+/816157 server implementation
    • #link https://review.opendev.org/c/openstack/python-novaclient/+/816158 novaclient
    • #link https://review.opendev.org/c/openstack/python-openstackclient/+/847792 openstackclient
    • Full disclosure: I will most likely not be present at todays weekly, but wanted to use the opportunity to bring this to your kind attention.

• #topic Stable Branches
  • #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
  • #info stable/train is blocked, fix exists but hasn't merged yet due to intermittent failures + now nova-grenade-multinode & nova-live-migration started to fail @ devstack 'create' phase

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

• #topic Open discussion
  • (bauzas) Opportunities for low-hanging-fruits, anyone ? (to be punted to next week)
  • (sean) https://review.opendev.org/c/openstack/nova-specs/+/849488 spec freeze exception for spice compression
  • (sean) there seams to be considerable outstanding question with regards to Configurable instance domains

"https://review.opendev.org/c/openstack/nova-specs/+/849765" to the point that i belive we should revert this. the question i then have is do we think we could come to an agreement before the next meeting on the open point (e.g. if we granted a spec freeze exception could we reasonable address the out standing issues) or should we defer this to AA so that we have time to evaluate this fully. The main concerns are rolling upgrades, is this in scope of nova, the ux between neutron and nova domain name configuration ("i already told neutron what domain to use why should i have to tell nova" vs " if i tell nova i don't need to configure neuton isn't that simpler") in aggregate I'm actually leaning towards taking a step back and revauating all options for step 0 incldueing reverting or sanitisation fo display names and allowing FQDNs in the hostname filed. i.e. should we have truncated instead of normalising as we do for unicode, should we allow the fqdn in the host name field but truncate it when setting dns_name on neutron ports. should we have a neutron extion to mark a port as the "primary domain". we had ruled out test options in the past at different point but we seam to have reached an impass where all options have negatives and we dislike them for different reason so we may need to evaluate them again with that new context. https://review.opendev.org/c/openstack/nova-specs/+/850048 revert proposed here

• • (melwitt) I will not be at the meeting today but in case you missed it, I'm seeking input regarding terminology used in the currently named "ephemeral encryption" feature spec and patches: https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029546.html. If you have thoughts on whether the terminology should be changed to something other than "ephemeral encryption", please comment on the ML thread or on this patch https://review.opendev.org/c/openstack/nova/+/764486 (thank you gibi for adding a comment 🙂)

Sub-teams

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

Previous meetings

• All other meetings are here