Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(→‎Agenda for next meeting)
(→‎Agenda for next meeting)
(45 intermediate revisions by 5 users not shown)
Line 37: Line 37:
 
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)
+
* May 13 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210513T160000)
−
* Feb 18 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210218T160000)
+
* May 20 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210520T160000)
−
* Feb 25 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210225T160000)
+
* 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.
Line 47: Line 48:
 
* #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 13 new untriaged bugs (+1 since the last meeting): #link 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 Gate status
 
* #topic Gate status
−
** gate on master feels OK to me
+
** 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
 
−
** #link https://etherpad.opendev.org/p/nova-runways-wallaby
 
−
** #link https://blueprints.launchpad.net/nova/+spec/nova-support-webvnc-with-password-anthentication : has negative feedback to work with
 
−
** #link https://blueprints.launchpad.net/nova/+spec/compact-db-migrations-wallaby : the nova db patches approved the nova_api db patches needs review
 
−
** #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 necessary patch has negativ feedback
 
  
 
* #topic Release Planning
 
* #topic Release Planning
−
** Feature Freeze is at 11th of March, in 4 weeks from now
+
** Milestone 1 is 27th of May. Nothing special is expected at that time.
 +
** As in previous cycles we plan to have spec freeze at M2 only.
 +
** See the nova specific schedule on #link https://wiki.openstack.org/wiki/Nova/Xena_Release_Schedule
  
 
* #topic Stable Branches
 
* #topic Stable Branches
−
**  
+
** 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
Line 71: Line 70:
  
 
* #topic Open discussion
 
* #topic Open discussion
−
** (kashyap; 05-FEB-2021) Late blueprint-approval request: https://blueprints.launchpad.net/nova/+spec/allow-disabling-cpu-flags
+
** (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.
−
*** 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 ==

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

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/Nova&oldid=178476"