Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

m (Agenda for next meeting)
(Agenda for next meeting)
 
(349 intermediate revisions by 26 users not shown)
Line 1: Line 1:
  
 
= Weekly Nova team meeting =
 
= Weekly Nova team meeting =
'''MEETING TIME: Thursdays  16:00 UTC (#openstack-meeting-3)'''
 
  
The Thursday 8:00 UTC slot is kept as a unofficial office hour on #openstack-nova for contributors who cannot attend on the official meeting slot.
+
''' Regular MEETING TIME: '''Tuesdays'''  16:00 UTC (#openstack-nova on OFTC)'''
  
 
This meeting is a weekly gathering of developers working on [[Nova|OpenStack Compute (Nova)]].  We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.
 
This meeting is a weekly gathering of developers working on [[Nova|OpenStack Compute (Nova)]].  We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.
Line 12: Line 11:
  
 
* #topic Release News
 
* #topic Release News
** #link Nova Victoria schedule https://wiki.openstack.org/wiki/Nova/Wallaby_Release_Schedule
+
** #link Nova Yoga schedule https://releases.openstack.org/yoga/schedule.html
  
 
* #topic Stable branch status
 
* #topic Stable branch status
** #link stable/victoria: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/victoria
+
** #link stable/zed: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/placement+OR+project:openstack/nova)+branch:stable/zed
** #link stable/ussuri: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/ussuri
+
** #link stable/yoga: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/placement+OR+project:openstack/nova)+branch:stable/yoga
** #link stable/train: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/train
+
** #link stable/xena: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/placement+OR+project:openstack/nova)+branch:stable/xena
** stable/stein is EM
+
** #link stable/wallaby is EM
  
 
* #topic Bugs (stuck/critical)
 
* #topic Bugs (stuck/critical)
Line 37: Line 36:
 
Next meetings scheduled for:
 
Next meetings scheduled for:
  
* Feb 4 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210204T160000)
+
* Nov 29 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-11-29T16:00:00)
* Feb 11 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210211T160000)
+
* Dec 06 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-12-06T16:00:00)
* Feb 18 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210218T160000)
+
* Dec 13 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-12-13T16:00:00)
 
+
* Dec 20 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-12-20T16:00:00)
  
  
Line 48: Line 47:
  
 
* #topic Bugs (stuck/critical)
 
* #topic Bugs (stuck/critical)
** No [https://bugs.launchpad.net/nova/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress Critical bugs]
+
** #info No [https://bugs.launchpad.net/nova/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress Critical bug]
** #link 12 new untriaged bugs (-5 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
+
** #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16 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 elodilles
  
 
* #topic Gate status
 
* #topic Gate status
** gate on master feels OK to me
+
** #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
** Please look at the gate failures, file a bug, and add an elastic-recheck signature in the opendev/elastic-recheck repo (example: #link https://review.opendev.org/#/c/759967)
+
** #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 Runway status
+
* #topic Release Planning
** #link https://etherpad.opendev.org/p/nova-runways-wallaby
+
** #link https://releases.openstack.org/antelope/schedule.html
** #link https://blueprints.launchpad.net/nova/+spec/nova-support-webvnc-with-password-anthentication : close to be ready. I was already +2 but Sean found an issue to be fixed
+
** #info Antelope-2 is in 5 weeks
** #link https://blueprints.launchpad.net/nova/+spec/compact-db-migrations-wallaby : the series has been approve up until Queens and slowly going through the gate
 
** #link https://blueprints.launchpad.net/nova/+spec/modernize-os-hypervisors-api : the api code landed, the python-novaclient patch and the policy patch needs some work
 
** #link https://blueprints.launchpad.net/nova/+spec/support-interface-attach-with-qos-ports : the last three patches needs a second set of eyes
 
  
* #topic Release Planning
+
* #topic Review priorities
** Feature Freeze is at 11th of March, in 5 weeks from now
+
** #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
 
* #topic Stable Branches
** victoria 22.1.0, ussuri 21.1.2, train 20.5.0 were released today
+
** #info stable branches seem to be unblocked / OK
** branches should be OK, no outstanding issue
+
** #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
  
 
* #topic Sub/related team Highlights
 
* #topic Sub/related team Highlights
** Libvirt (bauzas)
+
** #info No subteam left
*** ?
 
  
 
* #topic Open discussion
 
* #topic Open discussion
** (gibi): The nova-core added to the placement-core gerrit group. Then we realized that we have a similar situation in the placement-stable-maint group. So I've made a similar proposal about it  #link http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020186.html Any objection?
+
** (IRC nickname) the topic you would want to discuss.
 
 
** (kashyap; 05-FEB-2021) Late blueprint-approval request: https://blueprints.launchpad.net/nova/+spec/allow-disabling-cpu-flags
 
*** I realize this is late in the cycle, but this really helps alleviate potential live migration problems on some Intel hardware during upgrades and updates.  This is technically a simple feature; but can also be considered a "bug fix" that unblocks live migration in some scenarios.
 
*** Main Benefit: The ability to selectively disable CPU features for a guest means: newly launched VMs on a compute node can now disable offending guest CPU flags that block live migration.  This facilitates live migration to a host with TSX=off.
 
*** Example: Today, a VM running on a compute node with Intel TSX=on (which is the default on all Linux kernels until v.5.11) cannot be migrated to a node with Intel TSX=off.  But, the ability to selectively disable CPU flags alleviates this (and similar problems) — you can now keep TSX enabled on a host, and yet block it for the guest via `cpu_model_extra_flags`.  This unblocks live-migrating the said guest to a host with TSX=off.
 
*** Notes: On relevant Intel processors, TSX is suggested to be disabled as it can be a potential security problem.  TSX is disabled by default upstream Linux v.5.11 (Oct-2019)
 
  
 
== Sub-teams ==
 
== Sub-teams ==

Latest revision as of 15:18, 29 November 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.

Agenda for next meeting

Next meetings scheduled for:


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

Here is the agenda for the next meeting:

  • #topic Sub/related team Highlights
    • #info No subteam left
  • #topic Open discussion
    • (IRC nickname) the topic you would want to discuss.

Sub-teams

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

Previous meetings