Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(Agenda for next meeting)
 
(140 intermediate revisions by 12 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 15: Line 16:
  
 
* #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/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
** stable/stein is EM
 
  
 
* #topic Bugs (stuck/critical)
 
* #topic Bugs (stuck/critical)
Line 37: Line 38:
 
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)
+
* Sept 21 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-09-21T16:00:00)
* Feb 11 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210211T160000)
+
* Sept 28 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-09-28T16:00:00)
* Feb 18 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210218T160000)
+
* 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.
Line 48: Line 49:
  
 
* #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]
** #link 12 new untriaged bugs (-5 since the last meeting): #link 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 Gate status
 
* #topic Gate status
** gate on master feels OK to me
+
** Nova gate bugs #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure
 +
** 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)
 
** 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 Runway status
+
* #topic Release Planning
** #link https://etherpad.opendev.org/p/nova-runways-wallaby
+
** Release tracking etherpad #link https://etherpad.opendev.org/p/nova-xena-rc-potential
** #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
+
** 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 https://blueprints.launchpad.net/nova/+spec/compact-db-migrations-wallaby : the series has been approve up until Queens and slowly going through the gate
+
** No bugfixes proposed yet in Nova for RC2
** #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
+
** We will need a Placement RC2 release due to #link https://review.opendev.org/c/openstack/placement/+/810001
** #link https://blueprints.launchpad.net/nova/+spec/support-interface-attach-with-qos-ports : the last three patches needs a second set of eyes
+
** Remember to propose regression bugfixes for a new RC with nova-xena-rc-potential
  
* #topic Release Planning
+
* #topic Review priorities
** Feature Freeze is at 11th of March, in 5 weeks from now
+
** 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
** ?
+
** 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
 
** Libvirt (bauzas)
 
** Libvirt (bauzas)
*** ?
 
  
 
* #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?
+
** (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 ==
 
== 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