Difference between revisions of "Meetings/Nova"
(→Agenda for next meeting) |
(→Agenda for next meeting) |
||
Line 60: | Line 60: | ||
* #topic Release Planning | * #topic Release Planning | ||
− | ** | + | ** This week we have "Final release for non-client libraries" |
− | *** os-vif | + | *** I think we are ready. os-vif did not need a new release since 2.0.0 |
− | *** os-resource-classes | + | *** I talked to tetsuro, he handles os-resource-classes and os-traits |
− | + | ** One week until Milestone 3 | |
− | ** | ||
− | |||
− | |||
** Feature freeze | ** Feature freeze | ||
− | *** from the 30 approved BPs for Ussuri | + | *** from the 30 approved BPs for Ussuri 10 have already been implemented(+2 since last week) \o/ |
− | *** | + | *** There are 9 open BPs still targeted to ussuri-3 #link https://launchpad.net/nova/+milestone/ussuri-3 |
** Final release for client libraries | ** Final release for client libraries | ||
− | *** | + | *** we have patches open to support the newly merged microversions, 2.83 and 2.84 #link https://review.opendev.org/#/q/project:openstack/python-novaclient+status:open |
+ | **** #link https://review.opendev.org/#/c/713089 2.83 | ||
+ | **** #link https://review.opendev.org/#/c/714561 2.84 | ||
* #topic Stable Branches | * #topic Stable Branches |
Revision as of 09:09, 2 April 2020
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 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
- stable/rocky is EM
- #topic Bugs (stuck/critical)
- No Critical bugs
- #link 108 new untriaged bugs (+6 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
- #link 36 untagged untriaged bugs (+6 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
- https://etherpad.openstack.org/p/nova-bug-triage-ussuri
- reporting etherpad https://etherpad.openstack.org/p/nova-bug-triage-ussuri
- #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: 417 (-7); Top score: 2670 (+3)
- #help Pick a patch near the top, shepherd it to closure
Agenda for next meeting
Next meetings scheduled for:
- April 2 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200402T160000)
- April 9 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200409T160000)
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-03-26-16.00.log.html
- Plans for a virtual PTG is still up on the ML #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013555.html
- Two company rule are less strict now as per #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013553.html
- We have two new cores lyarwood and gmann. Welcome! \o/
- #topic Bugs (stuck/critical)
- No Critical bugs
- #link 108 new untriaged bugs (+6 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
- #topic Gate status
- melwitt, lyarwood, gmann: how is the gate doing recently?
- #topic Release Planning
- This week we have "Final release for non-client libraries"
- I think we are ready. os-vif did not need a new release since 2.0.0
- I talked to tetsuro, he handles os-resource-classes and os-traits
- One week until Milestone 3
- Feature freeze
- from the 30 approved BPs for Ussuri 10 have already been implemented(+2 since last week) \o/
- There are 9 open BPs still targeted to ussuri-3 #link https://launchpad.net/nova/+milestone/ussuri-3
- Final release for client libraries
- we have patches open to support the newly merged microversions, 2.83 and 2.84 #link https://review.opendev.org/#/q/project:openstack/python-novaclient+status:open
- #link https://review.opendev.org/#/c/713089 2.83
- #link https://review.opendev.org/#/c/714561 2.84
- we have patches open to support the newly merged microversions, 2.83 and 2.84 #link https://review.opendev.org/#/q/project:openstack/python-novaclient+status:open
- This week we have "Final release for non-client libraries"
- #topic Stable Branches
- lyarwood: anything newsworthy?
- #topic Sub/related team Highlights
- Placement (tetsuro)
- ?
- API (gmann)
- 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.
- (brinzhang_): https://review.opendev.org/#/q/topic:bp/destroy-instance-with-datavolume is stuck on whether we want a PATCH API or not.
- In the possible API design is discussed in the spec #link https://review.opendev.org/#/c/580336/28/specs/ussuri/approved/destroy-instance-with-datavolume.rst@43 and on the nova meeting #link http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-02-20-14.00.log.html#l-62
- Now we are discussing the API design again in the implementation #link https://review.opendev.org/#/c/693828/19/nova/api/openstack/wsgi.py@54
- dansmith seems to be worrying about the impl as this will be the first PATCH method in nova.
- (brinzhang_): https://review.opendev.org/#/q/topic:bp/destroy-instance-with-datavolume is stuck on whether we want a PATCH API or not.
- 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
- (gibi): Note that this weekend EU goes to summer time (e.g. I will go from UTC + 1 to UTC + 2) but the meeting remains at 16:00 UTC.
Sub-teams
There are also some Nova subteam meetings. See Nova#Nova_subteams for details.