Difference between revisions of "Meetings/NovaScheduler"
< Meetings
Eric Fried (talk | contribs) (→Agenda for next meeting) |
Eric Fried (talk | contribs) (→Previous meetings) |
||
| Line 40: | Line 40: | ||
== Previous meetings == | == Previous meetings == | ||
| + | * [http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-01-08-14.00.log.html 2018.01.08] | ||
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-12-18-14.00.log.html 2017.12.18] | * [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-12-18-14.00.log.html 2017.12.18] | ||
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-12-11-14.00.log.html 2017.12.11] | * [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-12-11-14.00.log.html 2017.12.11] | ||
Revision as of 16:05, 8 January 2018
Contents
Weekly Nova Scheduler team meeting
MEETING TIME: Mondays 14:00 UTC (#openstack-meeting-alt)
This meeting is a weekly gathering of developers working on the Nova Scheduler subteam. We cover topics such as development focus, status, bugs, reviews, and other current topics worthy of real-time discussion.
NOTE: this wiki page should be 'emptied' at the end of each meeting.
Next meetings scheduled for:
- No meetings December 25 and January 1
- January 8 2018 1400 UTC, #openstack-meeting-alt
- January 15 2018 1400 UTC, #openstack-meeting-alt
Agenda for next meeting
- Specs & Reviews
- Reviews
- Nested RPs:
- ComputeDriver.update_provider_tree() series starting with: https://review.openstack.org/#/c/521685/ (efried) (See open discussion topics)
- Nested affordance in GET /allocation_candidates series starting with: https://review.openstack.org/#/c/531443/1 (jaypipes)
- Granular resource requests (efried): https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/granular-resource-requests (waiting for ^^)
- Alternate hosts (edleafe):
- Series now starts with test case patch https://review.openstack.org/#/c/531022/
- Revealed bug: https://bugs.launchpad.net/nova/+bug/1741125
- Nested RPs:
- Reviews
- Bugs
- Placement bugs
- Open discussion
- Using /allocation_candidates?limit= from nova-side, should we? how?
- WIP: https://review.openstack.org/#/c/531517/ (dansmith)
- sharing providers in ProviderTree: https://review.openstack.org/#/c/526539/
- If sharing providers are managed by compute nodes, how does coordination work? Answer: careful handling of conflicts
- Generation support needed for PUT /rp/{uuid}/aggregates
- Sensible reGET/retry on 409s
- Can we centralize all that logic in the report client and have it work for all cases, or do virt drivers need more control? (Related to below.)
- If sharing providers are managed by compute nodes, how does coordination work? Answer: careful handling of conflicts
- Why can't (in-tree) virt drivers talk to placement? See conversation seeds in patch-level comments on https://review.openstack.org/#/c/526539/7
- Using /allocation_candidates?limit= from nova-side, should we? how?
