Difference between revisions of "Meetings/Nova"
< Meetings
(→Agenda for next meeting) |
Eric Fried (talk | contribs) (→Weekly Nova team meeting) |
||
Line 20: | Line 20: | ||
* #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 | + | ** #link 90 new untriaged bugs (+2 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New |
− | ** #link | + | ** #link 15 untagged untriaged bugs (+2 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 31: | Line 31: | ||
* #topic Review status page | * #topic Review status page | ||
** #link http://status.openstack.org/reviews/#nova | ** #link http://status.openstack.org/reviews/#nova | ||
− | ** Count: | + | ** Count: 442 (+2); Top score: 3376 (+21) |
** #help Pick a patch near the top, shepherd it to closure | ** #help Pick a patch near the top, shepherd it to closure | ||
Revision as of 14:02, 6 February 2020
Contents
Weekly Nova team meeting
MEETING TIME: Thursdays alternating 14:00 UTC (#openstack-meeting) and 21:00 UTC (#openstack-meeting)
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 Ussuri schedule https://wiki.openstack.org/wiki/Nova/Ussuri_Release_Schedule
- #topic Stable branch status
- #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
- #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)
- No Critical bugs
- #link 90 new untriaged bugs (+2 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
- #link 15 untagged untriaged bugs (+2 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
- #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 (dead) http://ciwatch.mmedvede.net/project?project=nova
- #topic Review status page
- #link http://status.openstack.org/reviews/#nova
- Count: 442 (+2); Top score: 3376 (+21)
- #help Pick a patch near the top, shepherd it to closure
Agenda for next meeting
Next meetings scheduled for:
- February 6 2020 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200206T140000)
- February 13 2020 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200213T210000)
Where you see "?" feel free to just edit the wiki and add your item.
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
- #link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-01-30-21.00.html
- #topic Bugs (stuck/critical)
- #topic Reminders
- SPEC FREEZE IS NEXT WEEK
- 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.
- #link etherpad for working the scrub (feel free to leave notes etc.) https://etherpad.openstack.org/p/nova-ussuri-planning
- #link ussuri blueprints https://blueprints.launchpad.net/nova/ussuri
- 22/42 Design:Approved, including 7 Implemented
- Rocky EM (lyarwood)
- SPEC FREEZE IS NEXT WEEK
- #topic PTG/Summit planning
- Please mark **attendance** and topics on
- #link PTG etherpad https://etherpad.openstack.org/p/nova-victoria-ptg
- #topic Sub/related team Highlights
- Placement (tetsuro)
- ?
- 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
- Placement (tetsuro)
- #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
- [huaqiang] the spec 'mixed cpu policy instance spec' still needs more input
- 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.
- #topic Open discussion
- https://blueprints.launchpad.net/nova/+spec/config-tsc-freq
- 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?
- https://blueprints.launchpad.net/nova/+spec/config-tsc-freq
Sub-teams
There are also some Nova subteam meetings. See Nova#Nova_subteams for details.