Difference between revisions of "Meetings/Nova"
< Meetings
(→Agenda for next meeting) |
Elod.illes (talk | contribs) (→Agenda for next meeting) |
||
| Line 60: | Line 60: | ||
* #topic Stable Branches | * #topic Stable Branches | ||
| − | **? | + | ** stable branch gates seem to be OK |
| + | ** train-em transition will happen within 2 weeks (2021-05-12) | ||
| + | ** final train release before the transition should be prepared as soon as possible (maybe around middle of next week?) | ||
| + | ** we should be careful what to merge before the final release, to avoid broken release that cannot be fixed, as there won't be any more train releases | ||
| + | ** on the other hand, if something should be merged, to be part of the final train release, then let us know -- e.g. in the etherpad: https://etherpad.opendev.org/p/nova-stable-train-em | ||
* #topic Sub/related team Highlights | * #topic Sub/related team Highlights | ||
Revision as of 14:12, 29 April 2021
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:
- April 22: No meeting this week as we have the PTG
- April 29 2021 16:00 UTC #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20210429T160000)
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 27 new untriaged bugs (+9 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
- #topic Gate status
- grenade job is failing. #link https://review.opendev.org/c/openstack/nova/+/778885 is on the gate to fix it
- Placement periodic job status #link <TODO link it to the result page when we have the job>
- 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 Release Planning
- The next release is in October. Nova specific schedule is on the wiki #link https://wiki.openstack.org/wiki/Nova/Xena_Release_Schedule
- #topic PTG planning
- Any feedback from last week, from the PTG?
- #topic Stable Branches
- stable branch gates seem to be OK
- train-em transition will happen within 2 weeks (2021-05-12)
- final train release before the transition should be prepared as soon as possible (maybe around middle of next week?)
- we should be careful what to merge before the final release, to avoid broken release that cannot be fixed, as there won't be any more train releases
- on the other hand, if something should be merged, to be part of the final train release, then let us know -- e.g. in the etherpad: https://etherpad.opendev.org/p/nova-stable-train-em
- #topic Sub/related team Highlights
- Libvirt (bauzas)
- ?
- Libvirt (bauzas)
- #topic Open discussion
- (sean)review priorities https://review.opendev.org/c/openstack/project-config/+/787523
- any objections to following gibis suggestion and making the range 0,+1 instead of -1..+2
- ?
- (sean)review priorities https://review.opendev.org/c/openstack/project-config/+/787523
Sub-teams
There are also some Nova subteam meetings. See Nova#Nova_subteams for details.
