Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(Agenda for next meeting)
 
(100 intermediate revisions by 9 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 11 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210211T160000)
+
* July 27 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-07-27T16:00:00)
* Feb 18 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210218T160000)
+
* Aug 3 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-08-03T16:00:00)
* Feb 25 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210225T160000)
+
* Aug 5 2021 '''8:00''' UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-08-05T08:00:00)
 +
* Aug 10 2021 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-08-10T16: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 47: 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 bugs]
** #link 12 new untriaged bugs (-5 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
+
** #link 11 new untriaged bugs (+1 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
  
 
* #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
+
** We past M2 and spec freeze. M3 is in 5 weeks.
** #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 have 21 approved an open blueprints and we have 5 weeks to finish them. Please focus review effort on bps in Needs Code Review state.
** #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
+
** Next deadline is non-client library freeze at 16th of August
** #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
 
** #link https://blueprints.launchpad.net/nova/+spec/support-interface-attach-with-qos-ports : the last three patches needs a second set of eyes
 
  
* #topic Release Planning
+
* #topic PTG Planning
** Feature Freeze is at 11th of March, in 5 weeks from now
+
** PTG timeslots booked by gibi, see #link http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023787.html
 +
** The PTG etherpad is ready to be filled with topics: #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
**  
+
** stable gates are not blocked
  
 
* #topic Sub/related team Highlights
 
* #topic Sub/related team Highlights
 
** Libvirt (bauzas)
 
** Libvirt (bauzas)
*** ?
+
*** Nope
  
 
* #topic Open discussion
 
* #topic Open discussion
** (kashyap; 05-FEB-2021) Late blueprint-approval request: https://blueprints.launchpad.net/nova/+spec/allow-disabling-cpu-flags
+
** (add your points here)
*** I realize this is late in the cycle, but this really helps alleviate potential live migration problems on some Intel hardware during upgrades and updates. This is technically a simple feature; but can also be considered a "bug fix" that unblocks live migration in some scenarios.
 
*** Main Benefit: The ability to selectively disable CPU features for a guest means: newly launched VMs on a compute node can now disable offending guest CPU flags that block live migration. This facilitates live migration to a host with TSX=off.
 
*** Example: Today, a VM running on a compute node with Intel TSX=on (which is the default on all Linux kernels until v.5.11) cannot be migrated to a node with Intel TSX=off. But, the ability to selectively disable CPU flags alleviates this (and similar problems) — you can now keep TSX enabled on a host, and yet block it for the guest via `cpu_model_extra_flags`. This unblocks live-migrating the said guest to a host with TSX=off.
 
*** Notes: On relevant Intel processors, TSX is suggested to be disabled as it can be a potential security problem. TSX is disabled by default upstream Linux v.5.11 (Oct-2019)
 
** (stephenfin) https://review.opendev.org/c/openstack/nova/+/772271 is stuck
 
*** elod is concerned about the backportability of this, as it has user-facing impacts. As noted by lyarwood though, the previous behavior was wrong
 
** (stephenfin) Outreachy projects?
 
*** I'm already helping mentor some NDSU students over in OSC/SDK land w/ diablo_rojo and gtema and could probably work with someone else. Do we have any nice, self-contained items that we'd like to do but just haven't had time for though?
 
*** /me thinks of things like PCI in placement (would need hardware though)
 
*** http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020288.html
 
  
 
== Sub-teams ==
 
== Sub-teams ==

Latest revision as of 15:16, 27 July 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 Release Planning
    • We past M2 and spec freeze. M3 is in 5 weeks.
    • We have 21 approved an open blueprints and we have 5 weeks to finish them. Please focus review effort on bps in Needs Code Review state.
    • Next deadline is non-client library freeze at 16th of August
  • #topic Stable Branches
    • stable gates are not blocked
  • #topic Sub/related team Highlights
    • Libvirt (bauzas)
      • Nope
  • #topic Open discussion
    • (add your points here)

Sub-teams

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

Previous meetings