Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(Agenda for next meeting)
(Agenda for next meeting)
 
(363 intermediate revisions by 23 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)'''
  
 
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 11:
  
 
* #topic Release News
 
* #topic Release News
** #link Nova Victoria schedule https://wiki.openstack.org/wiki/Nova/Victoria_Release_Schedule
+
** #link Nova Yoga schedule https://releases.openstack.org/yoga/schedule.html
  
 
* #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/yoga: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/yoga
** #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/xena: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/xena
** #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/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/stein: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/stein
+
** #link stable/victoria is EM
** stable/rocky is EM
 
  
 
* #topic Bugs (stuck/critical)
 
* #topic Bugs (stuck/critical)
**[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 10 new untriaged bugs (+3 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
 
** #link 4 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 41: Line 36:
 
Next meetings scheduled for:
 
Next meetings scheduled for:
  
* Nov 05 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20201105T160000)
+
* Sep 20 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-09-20T16:00:00)
* Nov 12 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20201112T160000)
+
* Sep 27 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-09-27T16:00:00)
 
+
* Oct 04 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-10-04T16:00:00)
 +
* Oct 11 2022 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-10-11T16: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 50: Line 46:
  
 
* #topic Bugs (stuck/critical)
 
* #topic Bugs (stuck/critical)
** 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 bugs]
+
** #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]
*** #link https://bugs.launchpad.net/nova/+bug/1902925
+
** #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 5 new untriaged bugs (+0 since the last meeting)
*** fix is up # link https://review.opendev.org/#/c/761458/
+
** #link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (+0 since the last meeting) in Storyboard for Placement
** #link 10 new untriaged bugs (+3 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
+
** #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
** #link 19 bugs in fix-commited state (+0 since last meeting): #link https://bugs.launchpad.net/nova/+bugs?field.searchtext=&search=Search&field.status%3Alist=FIXCOMMITTED
+
** #info bug baton is being passed to elodilles
*** if the bug is fixed on master then the bug should be in fix-released state
 
** #link 72 bugs are in INPROGRESS state without any tag: #link https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=INPROGRESS
 
*** these are potentially un-triaged bugs. Check if they are still valid
 
  
 +
* #topic Gate status
 +
** #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
 +
** #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
 +
** #link https://zuul.openstack.org/builds?job_name=tempest-integrated-compute-centos-9-stream&project=openstack%2Fnova&pipeline=periodic-weekly Centos 9 Stream periodic job status
 +
** #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs
 +
** #info Please look at the gate failures and file a bug report with the gate-failure tag.
 +
** #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures
  
* #topic Gate status
 
** 15 (+0 since the last meeting) unclassified gate failures, classification rate 46% (+0 since the last meeting) #link http://status.openstack.org/elastic-recheck/data/integrated_gate.html
 
** 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
** Wallaby Milestone 1 is on 3rd of December, which is 4 weeks from now
+
** #link https://releases.openstack.org/zed/schedule.html
** We should focus on updating / reviewing spec based on the PTG discussions
+
** #info RC1 was last Thursday
 +
** #info RC2 is planned this Thursday as we found one regression
 +
** #link https://etherpad.opendev.org/p/nova-zed-rc-potential Zed RC tracking etherpad
 +
 
 +
* #topic PTG planning
 +
** #link https://etherpad.opendev.org/p/nova-antelope-ptg Antelope PTG etherpad
 +
** #link https://ptg.opendev.org/ptg.html PTG schedule
 +
** shall we use a separate etherpad for ops-friendly sessions on Tuesday and Wednesday ?
 +
 
 +
* #topic Review priorities
 +
** #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2)
  
 
* #topic Stable Branches
 
* #topic Stable Branches
** the number of patches in stable branches, that are waiting for review, is growing
+
** #info stable/yoga is blocked by openstacksdk-functional-devstack job -- proposed fix: https://review.opendev.org/c/openstack/openstacksdk/+/858268
** '''final''' release for Stein before the transition to Extended Maintenance -- https://review.opendev.org/#/c/761614/
+
** #info stable/stein (and older) are blocked: grenade and other devstack based jobs fail with the same timeout issue as stable/train was previously
** also it's a good time to release on newer branches -- https://review.opendev.org/#/q/project:openstack/releases+is:open+intopic:nova
+
** #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
** (in case of victoria release, wait for bugfix of bug/1902925 to land first)
 
  
 
* #topic Sub/related team Highlights
 
* #topic Sub/related team Highlights
** API (gmann)
+
** #info No subteam left
*** ?
 
** Libvirt (bauzas)
 
*** ?
 
  
 
* #topic Open discussion
 
* #topic Open discussion
** (gibi): we said on the PTG that the cyborg bp https://blueprints.launchpad.net/nova/+spec/cyborg-shelve-and-unshelve is OK but we thought at that time that this is spec re-propose. It is actually a specless bp that we approved for Victoria. Are we OK to approve it to Wallaby?
+
** Add support for setting min/max unit for the VCPU and MEMORY_MB resource-providers in placement to values other than 1/all. Can configuration-options be OK for this, or are other approaches prefferred? See suggested use of configuration-options at https://review.opendev.org/c/openstack/nova/+/857595
*** ready to review implementation patch: #link https://review.opendev.org/#/c/729563/
+
** (add yours below)
** (gibi) there is another specless bp from cyborg https://blueprints.launchpad.net/nova/+spec/cyborg-suspend-and-resume this is a new one. Are we OK to approve the bp to Wallaby?
 
*** WIP patch: #link https://review.opendev.org/#/c/729945/
 
  
 
== Sub-teams ==
 
== Sub-teams ==

Latest revision as of 16:00, 20 September 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
    • Add support for setting min/max unit for the VCPU and MEMORY_MB resource-providers in placement to values other than 1/all. Can configuration-options be OK for this, or are other approaches prefferred? See suggested use of configuration-options at https://review.opendev.org/c/openstack/nova/+/857595
    • (add yours below)

Sub-teams

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

Previous meetings