Jump to: navigation, search

Difference between revisions of "Meetings/NovaScheduler"

m (Agenda for next meeting)
(Weekly Nova Scheduler team meeting)
Line 8: Line 8:
  
 
=== Next meetings scheduled for: ===
 
=== 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 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)
 
* January 30 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170130T140000)
 +
* February 6 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170206T140000)
  
 
== Agenda for next meeting ==
 
== Agenda for next meeting ==
  
 
* Specs & Reviews
 
* Specs & Reviews
** Inventory Tree: https://review.openstack.org/#/c/415920
+
** TBD
*** Is it possible to fix libvirt instead?
 
  
 
* Bugs
 
* Bugs
Line 23: Line 21:
  
 
* Open discussion
 
* 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.
+
** TBD
*** Also, related to the above, will 'can_host' be part of the object model for ResourceProviders?
 
  
 
== Previous meetings ==
 
== Previous meetings ==
  
 +
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-01-16-14.00.log.html 2017.01.16]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-01-09-14.00.log.html 2017.01.09]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-01-09-14.00.log.html 2017.01.09]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-01-02-14.01.log.html 2017.01.02]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-01-02-14.01.log.html 2017.01.02]
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-12-12-14.00.log.html 2016.12.12]
 
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/ All other meetings are here]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/ All other meetings are here]
  

Revision as of 17:38, 20 January 2017

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:

Agenda for next meeting

  • Specs & Reviews
    • TBD
  • Bugs
    • TBD
  • Open discussion
    • TBD

Previous meetings