Meetings/Nova
< Meetings
Contents
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.
- #topic Release News
- #link Nova Victoria schedule https://wiki.openstack.org/wiki/Nova/Wallaby_Release_Schedule
- #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/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/stein is EM
- #topic Bugs (stuck/critical)
- #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags
- #help need help with bug triage
- #topic Gate status
- #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
- #link 3rd party CI status (not so dead) http://ciwatch.mmedvede.net/project?project=nova
- #topic Review status page
- #link http://status.openstack.org/reviews/#nova
- Count: 438 (+20); Top score: 2303 (+21) (last refresh was 09-03)
- #help Pick a patch near the top, shepherd it to closure
Agenda for next meeting
Next meetings scheduled for:
- Feb 4 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210204T160000)
- Feb 11 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210211T160000)
- Feb 18 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210218T160000)
Where you see "?" feel free to just edit the wiki and add your item.
Here is the agenda for the next meeting:
- #topic Bugs (stuck/critical)
- No Critical bugs
- #link 12 new untriaged bugs (-5 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
- #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 Runway status
- #link https://etherpad.opendev.org/p/nova-runways-wallaby
- #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
- #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
- #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
- Feature Freeze is at 11th of March, in 5 weeks from now
- #topic Stable Branches
- victoria 22.1.0, ussuri 21.1.2, train 20.5.0 were released today
- branches should be OK, no outstanding issue
- #topic Sub/related team Highlights
- Libvirt (bauzas)
- ?
- Libvirt (bauzas)
- #topic Open discussion
- (gibi): The nova-core added to the placement-core gerrit group. Then we realized that we have a similar situation in the placement-stable-maint group. So I've made a similar proposal about it #link http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020186.html Any objection?
- (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)
- (kashyap; 05-FEB-2021) Late blueprint-approval request: https://blueprints.launchpad.net/nova/+spec/allow-disabling-cpu-flags
Sub-teams
There are also some Nova subteam meetings. See Nova#Nova_subteams for details.
