Difference between revisions of "Meetings/Nova"
< Meetings
(→Agenda for next meeting) |
(→Agenda for next meeting) |
||
| Line 59: | Line 59: | ||
* #topic Stuck Reviews | * #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. | ** 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. | ||
| − | *** Spec: Use PCPU and VCPU in one instance: https://review.opendev.org/#/c/668656/. We have agreements in PTG meeting on the following aspects but during recent review process some different opinions raised: | + | ***[Huaqiang] Spec: Use PCPU and VCPU in one instance: https://review.opendev.org/#/c/668656/. We have agreements in PTG meeting on the following aspects but during recent review process some different opinions raised: |
**** Specifying instance dedicated CPU mask vs specifying CPU count. Sean-k-mooney raised a flavor example for using CPU mask proposal in this place: https://review.opendev.org/#/c/668656/14/specs/ussuri/approved/use-pcpu-vcpu-in-one-instance.rst Line#146 | **** Specifying instance dedicated CPU mask vs specifying CPU count. Sean-k-mooney raised a flavor example for using CPU mask proposal in this place: https://review.opendev.org/#/c/668656/14/specs/ussuri/approved/use-pcpu-vcpu-in-one-instance.rst Line#146 | ||
**** Keep the interface of creating 'mixed' instance through 'resources:PCPU' and 'resources:VCPU' vs removing this interface. In L253, sean-k-mooney thinks that keeping the interface will cause issues with NUMA mechanism. | **** Keep the interface of creating 'mixed' instance through 'resources:PCPU' and 'resources:VCPU' vs removing this interface. In L253, sean-k-mooney thinks that keeping the interface will cause issues with NUMA mechanism. | ||
Revision as of 13:50, 9 January 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
- #topic Bugs (stuck/critical)
- No Critical bugs
- #link 97 new untriaged bugs (+1 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
- #link 12 untagged untriaged bugs (+0 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 again) http://ciwatch.mmedvede.net/project?project=nova
- #topic Review status page
- #link http://status.openstack.org/reviews/#nova
- Count: 457 (-2); Top score: 3877 (+21)
- #help Pick a patch near the top, shepherd it to closure
Agenda for next meeting
Next meetings scheduled for:
- January 09 2020 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200109T140000)
- January 16 2020 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200116T210000)
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/2019/nova.2019-12-12-14.00.html
- #topic Bugs (stuck/critical)
- #topic Reminders
- #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.
- [Huaqiang] Spec: Use PCPU and VCPU in one instance: https://review.opendev.org/#/c/668656/. We have agreements in PTG meeting on the following aspects but during recent review process some different opinions raised:
- Specifying instance dedicated CPU mask vs specifying CPU count. Sean-k-mooney raised a flavor example for using CPU mask proposal in this place: https://review.opendev.org/#/c/668656/14/specs/ussuri/approved/use-pcpu-vcpu-in-one-instance.rst Line#146
- Keep the interface of creating 'mixed' instance through 'resources:PCPU' and 'resources:VCPU' vs removing this interface. In L253, sean-k-mooney thinks that keeping the interface will cause issues with NUMA mechanism.
- [Huaqiang] Spec: Use PCPU and VCPU in one instance: https://review.opendev.org/#/c/668656/. We have agreements in PTG meeting on the following aspects but during recent review process some different opinions raised:
- 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
Sub-teams
There are also some Nova subteam meetings. See Nova#Nova_subteams for details.
