Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(Agenda for next meeting)
(Agenda for next meeting)
Line 36: Line 36:
 
Next meetings scheduled for:
 
Next meetings scheduled for:
  
* June 14 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-06-14T16:00:00)
 
 
* June 21 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-06-21T16:00:00)
 
* June 21 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-06-21T16:00:00)
 
* June 28 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-06-28T16:00:00)
 
* June 28 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-06-28T16:00:00)
 
* July 05 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-07-05T16:00:00)
 
* July 05 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-07-05T16:00:00)
 +
* July 12 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-07-05T16: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 46: Line 46:
  
 
* #topic Bugs (stuck/critical)
 
* #topic Bugs (stuck/critical)
** #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]
+
** #info One [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 https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 14 new untriaged bugs (+0 since the last meeting)
+
** #link https://bugs.launchpad.net/nova/+bug/1979047 Centos 9 Stream bug failure
 +
** #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 12 new untriaged bugs (-2 since the last meeting)
 
** #link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (0 since the last meeting) in Storyboard for Placement  
 
** #link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (0 since the last meeting) in Storyboard for Placement  
 
** #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
 
** #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
Line 61: Line 62:
 
* #topic Release Planning
 
* #topic Release Planning
 
** #link https://releases.openstack.org/zed/schedule.html
 
** #link https://releases.openstack.org/zed/schedule.html
** #info Zed-2 is in 4 weeks
+
** #info Zed-2 is in 3.5 weeks
 
+
** #startvote Spec review day on July 5th ? (yes/no)
* #topic OpenInfra Summit
 
** #info bauzas, gibi and stephenfin attended the summit
 
** #info Nova meet-and-greet Operators feedback session on Wednesday,  June 8, 2:50pm - 3:20pm got positive feedback
 
** #link https://etherpad.opendev.org/p/r.ea2e9bd003ed5aed5e25cd8393cf9362 readonly etherpad of the meet-and-greet session
 
  
 
* #topic Review priorities
 
* #topic Review priorities
Line 83: Line 80:
 
* #topic Open discussion
 
* #topic Open discussion
 
** (artom) Can we revisit stable func test backport policy? Specific patch stack: https://review.opendev.org/c/openstack/nova/+/791480/1 Previously we didn't want to backport func test infrastructure because it just offloads the backport debt onto whoever is doing backport for older than train releases. Some time has passed now, are there still operators running < stable/train and needing backports? https://etherpad.opendev.org/p/r.ea2e9bd003ed5aed5e25cd8393cf9362 indicates a majority of "train or older", but how many are on the "older" half of that?
 
** (artom) Can we revisit stable func test backport policy? Specific patch stack: https://review.opendev.org/c/openstack/nova/+/791480/1 Previously we didn't want to backport func test infrastructure because it just offloads the backport debt onto whoever is doing backport for older than train releases. Some time has passed now, are there still operators running < stable/train and needing backports? https://etherpad.opendev.org/p/r.ea2e9bd003ed5aed5e25cd8393cf9362 indicates a majority of "train or older", but how many are on the "older" half of that?
 +
** (bauzas) Opportunities for low-hanging-fruits, anyone ? (only if we have time left)
  
 
== Sub-teams ==
 
== Sub-teams ==

Revision as of 14:03, 21 June 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
    • (artom) Can we revisit stable func test backport policy? Specific patch stack: https://review.opendev.org/c/openstack/nova/+/791480/1 Previously we didn't want to backport func test infrastructure because it just offloads the backport debt onto whoever is doing backport for older than train releases. Some time has passed now, are there still operators running < stable/train and needing backports? https://etherpad.opendev.org/p/r.ea2e9bd003ed5aed5e25cd8393cf9362 indicates a majority of "train or older", but how many are on the "older" half of that?
    • (bauzas) Opportunities for low-hanging-fruits, anyone ? (only if we have time left)

Sub-teams

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

Previous meetings