Difference between revisions of "Meetings/NovaScheduler"
< Meetings
(→Agenda for next meeting) |
(→Agenda for next meeting) |
||
Line 23: | Line 23: | ||
* Open discussion | * Open discussion | ||
− | ** (edleafe - not attending, but will read the meeting logs) Are we going to allow 'can_host' as a query parameter? IOW, should the API allow a request to distinguish between compute nodes and shared disk providers when requesting DISK_GB resources? Currently you cannot pass 'can_host=1' as a query parameter, since we only support 'name', 'uuid', 'member_of', and 'resources' as valid params. | + | ** (edleafe - not attending, but will read the meeting logs) Are we going to allow 'can_host' (or 'shared', or whatever we call it) as a query parameter? IOW, should the API allow a request to distinguish between compute nodes and shared disk providers when requesting DISK_GB resources? Currently you cannot pass 'can_host=1' as a query parameter, since we only support 'name', 'uuid', 'member_of', and 'resources' as valid params. |
== Previous meetings == | == Previous meetings == |
Revision as of 20:12, 13 January 2017
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 16 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170116T140000)
- edleafe will not be available; cdent to run meeting
- January 23 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170123T140000)
- January 30 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170130T140000)
Agenda for next meeting
- Specs & Reviews
- Inventory Tree: https://review.openstack.org/#/c/415920
- Is it possible to fix libvirt instead?
- Inventory Tree: https://review.openstack.org/#/c/415920
- Bugs
- TBD
- Open discussion
- (edleafe - not attending, but will read the meeting logs) Are we going to allow 'can_host' (or 'shared', or whatever we call it) as a query parameter? IOW, should the API allow a request to distinguish between compute nodes and shared disk providers when requesting DISK_GB resources? Currently you cannot pass 'can_host=1' as a query parameter, since we only support 'name', 'uuid', 'member_of', and 'resources' as valid params.