Jump to: navigation, search

Difference between revisions of "Meetings/NovaScheduler"

m (→‎Previous meetings)
(→‎Weekly Nova Scheduler team meeting)
Line 16: Line 16:
  
 
* Specs & Reviews
 
* Specs & Reviews
−
** TBD
+
** Getting a list of filtered RPs
 +
*** https://review.openstack.org/#/c/392569/
 +
** 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:
 +
*** https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/custom-resource-classes
 +
** Placement Docs
 +
*** https://review.openstack.org/#/c/409340/
  
 
* Bugs
 
* Bugs
−
** TBD
+
** API not returning aggregate UUIDs: https://bugs.launchpad.net/nova/+bug/1652642
 +
*** Fix: https://review.openstack.org/#/c/415031/
 +
*** Spec: https://review.openstack.org/#/c/415511/
 +
** Allocation bad input handling and dead code fixing
 +
*** https://review.openstack.org/#/c/416751/
 +
 
  
 
* Open discussion
 
* Open discussion
−
** When/How do we want to get started on client code?
+
** cdent: ''can_host, aggregates in filtering''
−
** TBD
+
*** 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.
 +
 
 +
 
 +
 
  
 
== Previous meetings ==
 
== Previous meetings ==
  
−
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-01-02-14.00.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/2016/nova_scheduler.2016-12-12-14.00.log.html 2016.12.12]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-12-05-14.00.log.html 2016.12.05]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-12-05-14.00.log.html 2016.12.05]

Revision as of 18:45, 6 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


  • 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.



Previous meetings

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/NovaScheduler&oldid=149630"