Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(Agenda for next meeting)
(Agenda for next meeting)
(177 intermediate revisions by 12 users not shown)
Line 12: Line 12:
  
 
* #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/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
 
** #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/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/stein is EM
** 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 22 new untriaged bugs (+2 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
 
** #link 3 untagged untriaged bugs (+3 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 26:
 
* #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: 392 (+9); Top score: 2051 (+42) (last refresh was 06-11)
+
** 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 37:
 
Next meetings scheduled for:
 
Next meetings scheduled for:
  
* June 4 2020 16:00 UTC, No meeting due to PTG
+
* May 13 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210513T160000)
* June 11 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=202006011T160000)
+
* May 20 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210520T160000)
* June 18 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=202006018T160000)
+
* May 27 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210527T160000)
 +
 
  
 
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 bugs]
** #link 22 new untriaged bugs (+2 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
+
** #link 12 new untriaged bugs (+0 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
  
* #topic Runways
+
* #topic Gate status
** Etherpad is up for Victoria #link https://etherpad.opendev.org/p/nova-runways-victoria
+
** Placement periodic job status #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly
** we have 3 open runway slots
+
** 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)
** There is one item in the queue: #link https://review.opendev.org/#/q/topic:bp/use-pcpu-and-vcpu-in-one-instance+status:open
 
*** the first ~7 patches in that series seems to be ready for a slot.
 
*** Stephen (patch owner) confirmed to have time to iterate on the patches in the next two weeks.
 
*** Do we have cores who could review that in the next two weeks?
 
  
 
* #topic Release Planning
 
* #topic Release Planning
** Victoria Milestone 1 is next week.  
+
** Milestone 1 is 27th of May. Nothing special is expected at that time.
** We have ~5 open specs #link https://review.opendev.org/#/q/project:openstack/nova-specs+status:open
+
** As in previous cycles we plan to have spec freeze at M2 only.
** Do we want a spec review day next week?
+
** See the nova specific schedule on #link https://wiki.openstack.org/wiki/Nova/Xena_Release_Schedule
  
 
* #topic Stable Branches
 
* #topic Stable Branches
** There is a stable/train release proposed https://review.opendev.org/#/c/734952
+
** stable gate should be OK for stein-wallaby (many intermittent failures though)
 +
** old stable branches (xenial based) seem to be hit by py35/pypi issue - https://zuul.opendev.org/t/openstack/build/d6a26e1a220149aea67fad87b99f2f93/log/logs/grenade.sh.txt#61-89
 +
** train-em patch waiting for the final train release https://review.opendev.org/c/openstack/releases/+/790761
 +
** open release patches: train 20.6.1, ussuri 21.2.1, victoria 22.2.1, wallaby 23.0.1-- https://review.opendev.org/q/project:openstack/releases+intopic:nova+status:open
  
 
* #topic Sub/related team Highlights
 
* #topic Sub/related team Highlights
** API (gmann)
 
*** ?
 
 
** Libvirt (bauzas)
 
** Libvirt (bauzas)
 
*** ?
 
*** ?
 
* #topic Stuck Reviews
 
**  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.
 
** ?
 
  
 
* #topic Open discussion
 
* #topic Open discussion
** (bauzas): Seeking approval for specless bp #link https://blueprints.launchpad.net/nova/+spec/offline-reshape-tool
+
** (artom) Can we move the meeting to another day? Tuesday? It would help the Red Hat Nova team with our internal team calls organization. I want to be absolutely clear that there is no pressure, and we'll figure our stuff out regardless of the outcome of this question.
** (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)
 
*** some discussion about it on IRC: #link http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2020-06-10.log.html#t2020-06-10T15:02:18
 
  
 
== Sub-teams ==
 
== Sub-teams ==

Revision as of 14:46, 13 May 2021

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.

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
    • Libvirt (bauzas)
      •  ?
  • #topic Open discussion
    • (artom) Can we move the meeting to another day? Tuesday? It would help the Red Hat Nova team with our internal team calls organization. I want to be absolutely clear that there is no pressure, and we'll figure our stuff out regardless of the outcome of this question.

Sub-teams

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

Previous meetings