Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(Agenda for next meeting)
(Agenda for next meeting)
 
(291 intermediate revisions by 17 users not shown)
Line 1: Line 1:
  
 
= Weekly Nova team meeting =
 
= Weekly Nova team meeting =
'''MEETING TIME: Thursdays alternating 14:00 UTC (#openstack-meeting) and 21:00 UTC (#openstack-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 [[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 10: Line 12:
  
 
* #topic Release News
 
* #topic Release News
** #link Nova Ussuri schedule https://wiki.openstack.org/wiki/Nova/Ussuri_Release_Schedule
+
** #link Nova Victoria schedule https://wiki.openstack.org/wiki/Nova/Wallaby_Release_Schedule
  
 
* #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/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
 
** #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/stein: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/stein
+
** stable/stein is EM
** #link stable/rocky: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/rocky
 
** gmann: Currently stable brnaches till stable/rocky are broken: Fix in progress: #link https://review.opendev.org/#/q/topic:fix-stable-gate+(status:open+OR+status:merged)
 
  
 
* #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]
 
** #link 88 new untriaged bugs (+3 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
 
** #link 13 untagged untriaged bugs (+3 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 27: Line 26:
 
* #topic Gate status
 
* #topic Gate status
 
** #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
 
** #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
** #link 3rd party CI status (dead) http://ciwatch.mmedvede.net/project?project=nova
+
** #link 3rd party CI status (not so dead) http://ciwatch.mmedvede.net/project?project=nova
  
 
* #topic Review status page
 
* #topic Review status page
 
** #link http://status.openstack.org/reviews/#nova
 
** #link http://status.openstack.org/reviews/#nova
** Count: 440 (-2); Top score: 3334 (+21)
+
** Count: 438 (+20); Top score: 2303 (+21) (last refresh was 09-03)
 
** #help Pick a patch near the top, shepherd it to closure
 
** #help Pick a patch near the top, shepherd it to closure
  
Line 38: Line 37:
 
Next meetings scheduled for:
 
Next meetings scheduled for:
  
* February 6 2020 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200206T140000)
+
* May 13 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210513T160000)
* February 13 2020 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200213T210000)
+
* May 20 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210520T160000)
 +
* 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.
  
 
Here is the agenda for the next meeting:
 
Here is the agenda for the next meeting:
* #topic Last meeting
 
** #link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-01-30-21.00.html
 
*** ACTION: sean-k-mooney to do the train implemented specs business
 
*** ACTION: lyarwood to curate rocky EM list
 
*** ACTION: lyarwood to propose train & stein releases
 
  
 
* #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 (+0 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
 +
 +
* #topic Gate status
 +
** 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)
  
* #topic Reminders
+
* #topic Release Planning
** SPEC FREEZE IS NEXT WEEK
+
** Milestone 1 is 27th of May. Nothing special is expected at that time.
*** At that time I'd like to do a pass through the Definition:Approved specs and decide which we should Direction:Approve and which we should defer.
+
** As in previous cycles we plan to have spec freeze at M2 only.  
*** #link etherpad for working the scrub (feel free to leave notes etc.) https://etherpad.openstack.org/p/nova-ussuri-planning
+
** See the nova specific schedule on #link https://wiki.openstack.org/wiki/Nova/Xena_Release_Schedule
*** #link ussuri blueprints https://blueprints.launchpad.net/nova/ussuri
 
*** 22/42 Design:Approved, including 7 Implemented
 
** Rocky EM (lyarwood)
 
*** #link open rocky patches https://review.opendev.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/rocky
 
  
* #topic PTG/Summit planning
+
* #topic Stable Branches
** Please mark **attendance** and topics on
+
** stable gate should be OK for stein-wallaby (many intermittent failures though)
** #link PTG etherpad https://etherpad.openstack.org/p/nova-victoria-ptg
+
** 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
** [[Meetings/Placement|Placement]] (tetsuro)
+
** Libvirt (bauzas)
 
*** ?
 
*** ?
** API (gmann)
 
**** gmann did not send the updated report this week. Last updates on ML: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012260.html
 
 
* #topic Stuck Reviews
 
**  Please note "stuck review" means a review where there is some disagreement that needs resolving. It's not for reviews that just haven't had attention, except for exceptional cases.
 
*** [huaqiang] the spec 'mixed cpu policy instance spec' still needs more input
 
**** # link Use PCPU and VCPU in one instance : https://review.opendev.org/#/c/668656/
 
**** placement-ess style interface ('resources:(P|V)CPU') vs legacy flavor style (eg: 'hw(:|_)numa_pinned_cpus')  interface through a CPU mask
 
  
 
* #topic Open discussion
 
* #topic Open discussion
** https://blueprints.launchpad.net/nova/+spec/config-tsc-freq
+
** (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.
*** https://etherpad.openstack.org/p/invtsc
 
*** proposal is to add the ability to expose an invariant tsc cpu flag and specify the frequency to allow live migration.
 
*** we previously discussed this and said it could be a specless blueprint if the blueprint content was sufficient. do we agree that it is?
 
  
 
== Sub-teams ==
 
== Sub-teams ==

Latest 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