Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(Agenda for next meeting)
(Agenda for next meeting)
 
(272 intermediate revisions by 16 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)'''
 +
 
 +
''' Extra Asia + EU meeting slot, first Thursday of every month 8:00 UTC  in #openstack-nova in 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 13:
  
 
* #topic Release News
 
* #topic Release News
** #link Nova Victoria schedule https://wiki.openstack.org/wiki/Nova/Victoria_Release_Schedule
+
** #link Nova Victoria schedule https://wiki.openstack.org/wiki/Nova/Wallaby_Release_Schedule
  
 
* #topic Stable branch status
 
* #topic Stable branch status
 +
** ** #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: 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/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/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/train: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/train
+
** stable/train is EM
** #link stable/stein: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/stein
 
** stable/rocky is EM
 
  
 
* #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]
 
** #link 20 new untriaged bugs (no change since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
 
** #link 0 untagged untriaged bugs (no change since the last meeting): https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW
 
 
** #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags
 
** #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags
 
** #help need help with bug triage
 
** #help need help with bug triage
Line 29: Line 27:
 
* #topic Gate status
 
* #topic Gate status
 
** #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
 
** #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
** #link 3rd party CI status (dead) http://ciwatch.mmedvede.net/project?project=nova
+
** #link 3rd party CI status (not so dead) http://ciwatch.mmedvede.net/project?project=nova
  
 
* #topic Review status page
 
* #topic Review status page
 
** #link http://status.openstack.org/reviews/#nova
 
** #link http://status.openstack.org/reviews/#nova
** Count: 383 (-8); Top score: 2009 (-6) (last refresh was 05-28)
+
** Count: 438 (+20); Top score: 2303 (+21) (last refresh was 09-03)
 
** #help Pick a patch near the top, shepherd it to closure
 
** #help Pick a patch near the top, shepherd it to closure
  
Line 40: Line 38:
 
Next meetings scheduled for:
 
Next meetings scheduled for:
  
* June 4 2020 16:00 UTC, No meeting due to PTG
+
* Sept 21 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-09-21T16:00:00)
* June 11 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=202006011T160000)
+
* Sept 28 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-09-28T16:00:00)
* June 18 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=202006018T160000)
+
* Oct 5 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-10-05T16:00:00)
 +
* Oct 7 2021 '''8:00''' UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-10-07T08:00:00)
 +
* Oct 12 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-10-12T16:00:00)
  
 
Where you see "?" feel free to just edit the wiki and add your item.
 
Where you see "?" feel free to just edit the wiki and add your item.
  
 
Here is the agenda for the next meeting:
 
Here is the agenda for the next meeting:
* #topic Last meeting
 
** #link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-05-28-16.00.log.html
 
  
 
* #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]
+
** 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]
** <TODO update it> #link 20 new untriaged bugs (0 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New  
+
** #link 13 new untriaged bugs (-0 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
 +
** no open bugs marked with xena-rc-potential tag #link https://bugs.launchpad.net/nova/+bugs?field.tag=xena-rc-potential
 +
** please start marking release critical bugs with xena-rc-potential tag
  
* #topic Runways
+
* #topic Gate status
** Etherpad is up for Victoria #link https://etherpad.opendev.org/p/nova-runways-victoria
+
** Nova gate bugs #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure
** We have 3 open Runway slots and the Queue is empty
+
** Placement periodic job status #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly
 +
** 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)
  
 
* #topic Release Planning
 
* #topic Release Planning
** Victoria Milestone 1 is next week. Do we want a spec review day next week?
+
** Release tracking etherpad #link https://etherpad.opendev.org/p/nova-xena-rc-potential
 +
** We now have RC1 releases for both Nova and Placement #link https://review.opendev.org/c/openstack/releases/+/808706 and https://review.opendev.org/c/openstack/releases/+/808713
 +
** No bugfixes proposed yet in Nova for RC2
 +
** We will need a Placement RC2 release due to #link https://review.opendev.org/c/openstack/placement/+/810001
 +
** Remember to propose regression bugfixes for a new RC with nova-xena-rc-potential
 +
 
 +
* #topic Review priorities
 +
** https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement)+label:Review-Priority%252B1
 +
 
 +
* #topic PTG Planning
 +
** every info is in the PTG etherpad #link https://etherpad.opendev.org/p/nova-yoga-ptg
 +
** If you see a need for a specific cross project section then please let me know
  
 
* #topic Stable Branches
 
* #topic Stable Branches
** lyarwood any news?
+
** nova's stable/ussuri and stable/train are blocked (due to latest virtualenv uses latest setuptools which removed use_2to3)
 +
*** the future proof solution would be to pin virtualenv during tox install for stable branches, otherwise new errors can appear with every new release of setuptools, virtualenv, etc
 +
*** until we decide about the right solution we can maybe set lower-constraints job as non-voting ( https://review.opendev.org/809955 )
 +
** probably placement branches have the same errors
  
 
* #topic Sub/related team Highlights
 
* #topic Sub/related team Highlights
** API (gmann)
 
*** ?
 
 
** Libvirt (bauzas)
 
** Libvirt (bauzas)
*** ?
 
  
* #topic Stuck Reviews
+
* #topic Open discussion
** Please note "stuck review" means a review where there is some disagreement that needs resolving. It's not for reviews that just haven't had attention, except for exceptional cases.
+
** (gibi): release liaison role
** ?
+
** (gibi): gathering opinions about the current lower-constraints failure.
 +
*** bottom line: on stable branches we are installing tox which installs virtualenv which bundles setuptools unconstrained. This now leads to that we cannot install decorator 3.4.0 on stable any more as it depends on "user_2to3" from setuptools but the recent setuptools 58.0 removed support for that.
 +
*** Options to resolve the situation
 +
**** bump decorator major version from 3.4.0 to 4.0.0 on stable branches. Does it against stable policy?
 +
**** pin virtualenv version on stable during tox install
 +
**** disable lower-constraints testing
  
* #topic Open discussion
+
** (add your points here)
** (bauzas): Seeking approval for specless bp #link https://blueprints.launchpad.net/nova/+spec/offline-reshape-tool
 
** (sean-k-mooney): Seeking approval for specless bp #link https://blueprints.launchpad.net/nova/+spec/cyborg-rebuild-and-evacuate
 
** (brinzhang): Seeking approval for specless bp #link https://blueprints.launchpad.net/nova/+spec/cyborg-shelve-and-unshelve
 
** (gibi): I will be on PTO between 27th of July and 3rd of August (and between Aug 10 - 24). 30th of July is Milestone 2 and spec freeze, so I would need a stand-in handling the freeze during that week.
 
** (stephenfin): Can we make the 'cherry-picked from' line in backports preferred instead of mandatory? They're definitely nice to have, but they incur pain for larger backports consisting of multiple patches per branch (change one patch higher up and you invalid all lower backports). Maybe use Gerrit's model (add -x for first backport since it's landed and ignore for anything older)
 
  
 
== Sub-teams ==
 
== Sub-teams ==

Latest revision as of 15:35, 21 September 2021

Weekly Nova team meeting

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

Extra Asia + EU meeting slot, first Thursday of every month 8:00 UTC in #openstack-nova in 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 Stable Branches
    • nova's stable/ussuri and stable/train are blocked (due to latest virtualenv uses latest setuptools which removed use_2to3)
      • the future proof solution would be to pin virtualenv during tox install for stable branches, otherwise new errors can appear with every new release of setuptools, virtualenv, etc
      • until we decide about the right solution we can maybe set lower-constraints job as non-voting ( https://review.opendev.org/809955 )
    • probably placement branches have the same errors
  • #topic Sub/related team Highlights
    • Libvirt (bauzas)
  • #topic Open discussion
    • (gibi): release liaison role
    • (gibi): gathering opinions about the current lower-constraints failure.
      • bottom line: on stable branches we are installing tox which installs virtualenv which bundles setuptools unconstrained. This now leads to that we cannot install decorator 3.4.0 on stable any more as it depends on "user_2to3" from setuptools but the recent setuptools 58.0 removed support for that.
      • Options to resolve the situation
        • bump decorator major version from 3.4.0 to 4.0.0 on stable branches. Does it against stable policy?
        • pin virtualenv version on stable during tox install
        • disable lower-constraints testing
    • (add your points here)

Sub-teams

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

Previous meetings