Difference between revisions of "Meetings/Nova"
< Meetings
(→Agenda for next meeting) |
(→Agenda for next meeting) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 21: | Line 21: | ||
* #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 102 new untriaged bugs (+3 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New |
** #link 30 untagged untriaged bugs (+4 since the last meeting): https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW | ** #link 30 untagged untriaged bugs (+4 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 | ||
| Line 59: | Line 59: | ||
* #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 102 new untriaged bugs (+3 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New |
| − | |||
** melwitt, lyarwood, gmann: how is the gate doing recently? | ** melwitt, lyarwood, gmann: how is the gate doing recently? | ||
| Line 70: | Line 69: | ||
*** I see nothing open that is a must-have for Ussuri. | *** I see nothing open that is a must-have for Ussuri. | ||
*** Who will propose the releases for these libs next week? | *** Who will propose the releases for these libs next week? | ||
| + | ** Two weeks until Milestone 3 | ||
| + | ** Feature freeze | ||
| + | *** from the 30 approved BPs for Ussuri 8 is already implemented \o/ | ||
| + | *** I did a quick scan an targeted 12 from the remaining 22 BPs to ussuri-3 #link https://launchpad.net/nova/+milestone/ussuri-3 These are the ones I feel still has chance to be finished before the freeze. | ||
| + | ** Final release for client libraries | ||
| + | *** we have patches open #link https://review.opendev.org/#/q/project:openstack/python-novaclient+status:open but these are still tight to open nova patches. | ||
* #topic Stable Branches | * #topic Stable Branches | ||
| Line 83: | Line 88: | ||
** 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. | ** 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. | *** (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. | ||
* #topic Open discussion | * #topic Open discussion | ||
Revision as of 13:08, 26 March 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 102 new untriaged bugs (+3 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
- #link 30 untagged untriaged bugs (+4 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:
- March 26 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200326T160000)
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-19-16.00.log.html
- gibi promised to follow up on the ML about the plans for a virtual PTG.
- proposal sent to the ML #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013555.html but I'm open to any suggestion about the format.
- We had a discussion about the two company rule last week.
- the resulting ML thread #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013423.html
- based on the different discussion I'm now proposing a compromise #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013553.html Please raise your voice if you don't like it til next Tuesday
- we discussed the core situation last week as well. It is resulted in a nomination of two new cores. Cores, please cast your votes on the ML til next Monday
- #topic Bugs (stuck/critical)
- No Critical bugs
- #link 102 new untriaged bugs (+3 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
- melwitt, lyarwood, gmann: how is the gate doing recently?
- #topic Release Planning
- One week until "Final release for non-client libraries" (Apr 3.)
- os-vif #link https://review.opendev.org/#/q/project:openstack/os-vif+status:open
- os-resource-classes #link https://review.opendev.org/#/q/project:openstack/os-resource-classes+status:open
- os-traits #link https://review.opendev.org/#/q/project:openstack/os-traits+status:open
- I see nothing open that is a must-have for Ussuri.
- Who will propose the releases for these libs next week?
- Two weeks until Milestone 3
- Feature freeze
- from the 30 approved BPs for Ussuri 8 is already implemented \o/
- I did a quick scan an targeted 12 from the remaining 22 BPs to ussuri-3 #link https://launchpad.net/nova/+milestone/ussuri-3 These are the ones I feel still has chance to be finished before the freeze.
- Final release for client libraries
- we have patches open #link https://review.opendev.org/#/q/project:openstack/python-novaclient+status:open but these are still tight to open nova patches.
- One week until "Final release for non-client libraries" (Apr 3.)
- #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.
