Meetings/NovaScheduler
< Meetings
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:
- January 9 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170109T140000)
- January 16 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170116T140000)
- edleafe will not be available
- January 23 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170123T140000)
Agenda for next meeting
- Specs & Reviews
- Getting a list of filtered RPs
- Placement Client?
- Miguelle Lavelle's work: https://github.com/miguellavalle/python-placementclient/tree/adding-grp-support
- Sylvain's addition of a PlacementClient: https://review.openstack.org/#/c/417111/2
- Resource Tracker cleanup series:
- Placement Docs
- Bugs
- API not returning aggregate UUIDs: https://bugs.launchpad.net/nova/+bug/1652642
- Allocation bad input handling and dead code fixing
- Open discussion
- cdent: can_host, aggregates in filtering
- There's still some confusion (from at least me) on whether the can_host field is relevant when making queries to filter resource providers. Similarly, when requesting resource providers to satisfy a set of resources, we don't (unless I've completely missed it) return resource providers (as compute nodes) that are associated with other resource providers (by aggregate) that can satisfy a resource requirement. Feels like we need to work backwards from a test or use case and see what's missing.
- cdent: can_host, aggregates in filtering
