Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

m
(Agenda for next meeting)
 
(434 intermediate revisions by 23 users not shown)
Line 1: Line 1:
  
 
= Weekly Nova team meeting =
 
= Weekly Nova team meeting =
'''MEETING TIME: Thursdays alternating 14:00 UTC (#openstack-meeting) and 21:00 UTC (#openstack-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 [[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.
  
NOTE: this wiki page should be 'emptied' at the end of each meeting.
+
== 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 Victoria schedule https://wiki.openstack.org/wiki/Nova/Wallaby_Release_Schedule
 +
 
 +
* #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
 +
** stable/train 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 ==
 
== Agenda for next meeting ==
Line 11: Line 38:
 
Next meetings scheduled for:
 
Next meetings scheduled for:
  
* October 03 2019 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20191003T140000)
+
* Sept 21 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-09-21T16:00:00)
* October 10 2019 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20191010T210000)
+
* Sept 28 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-09-28T16:00:00)
 +
* 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/2019/nova.2019-09-26-21.00.html
 
  
* #topic Release News
+
* #topic Bugs (stuck/critical)
** RC1 is out, stable/train is forked, master is ussuri
+
** 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 Release todos: https://etherpad.openstack.org/p/nova-train-release-todo
+
** #link 13 new untriaged bugs (-0 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
** #link Nova Ussuri schedule seeded https://wiki.openstack.org/wiki/Nova/Ussuri_Release_Schedule
+
** 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 Summit/PTG Planning
+
* #topic Gate status
** Ussuri scope containment
+
** Nova gate bugs #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure
*** #link start of thread http://lists.openstack.org/pipermail/openstack-discuss/2019-September/thread.html#9832
+
** Placement periodic job status #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly
*** #link continued http://lists.openstack.org/pipermail/openstack-discuss/2019-October/thread.html#9835
+
** 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 Spec template update for "core liaison" https://review.opendev.org/#/c/685857/
 
  
* #topic Stable branch status
+
* #topic Release Planning
** #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
+
** Release tracking etherpad #link https://etherpad.opendev.org/p/nova-xena-rc-potential
** #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
+
** 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
** #link stable/rocky: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/rocky
+
** No bugfixes proposed yet in Nova for RC2
** #link stable/queens: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/queens
+
** 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 Bugs (stuck/critical)
+
* #topic Review priorities
** 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]
+
** https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement)+label:Review-Priority%252B1
** #link 74 new untriaged bugs (+2 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
 
** #link 3 untagged untriaged bugs (-1 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
 
** #help need help with bug triage
 
  
* #topic Gate status
+
* #topic PTG Planning
** #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
+
** every info is in the PTG etherpad #link https://etherpad.opendev.org/p/nova-yoga-ptg
** #link 3rd party CI status (seems to be back in action) http://ciwatch.mmedvede.net/project?project=nova
+
** If you see a need for a specific cross project section then please let me know
  
* #topic Reminders
+
* #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
 
* #topic Sub/related team Highlights
** [[Meetings/Placement|Placement]] (cdent/tetsuro)
+
** Libvirt (bauzas)
*** ?
 
** API (gmann)
 
**** ?
 
  
* #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.
* #topic Review status page
+
*** 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.
** #link http://status.openstack.org/reviews/#nova
+
*** Options to resolve the situation
** Count: 457 (+2); Top score: 2091 (-444 \o/)
+
**** bump decorator major version from 3.4.0 to 4.0.0 on stable branches. Does it against stable policy?
** #help Pick a patch near the top, shepherd it to closure
+
**** pin virtualenv version on stable during tox install
 +
**** disable lower-constraints testing
  
* #topic Open discussion
+
** (add your points here)
** #help Volunteer needed to update the contributor guide (see https://review.opendev.org/#/c/685630/)
 
** Specless BP approval https://blueprints.launchpad.net/nova/+spec/remove-nova-network-ussuri
 
  
 
== 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