Jump to: navigation, search


< Meetings
Revision as of 12:27, 11 February 2021 by Gibi (talk | contribs) (Agenda for next 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.

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 Gate status
    • gate on master feels OK to me
    • 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
    • Feature Freeze is at 11th of March, in 4 weeks from now
  • #topic Stable Branches
  • #topic Sub/related team Highlights
    • Libvirt (bauzas)
      •  ?
  • #topic Open discussion
    • (kashyap; 05-FEB-2021) Late blueprint-approval request: https://blueprints.launchpad.net/nova/+spec/allow-disabling-cpu-flags
      • 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?


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

Previous meetings