Jump to: navigation, search

Difference between revisions of "Meetings/NovaScheduler"

 
(206 intermediate revisions by 8 users not shown)
Line 1: Line 1:
  
= Weekly Nova Scheduler team meeting =
+
The Nova Scheduler meeting is being moved back into the main [[Meetings/Nova|Nova]] meeting and the original timeslot will be the [[Meetings/Placement|Placement]] meeting. It will be common for nova's use of placement to be a topic at the meeting. Don't worry. It's okay.
'''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.
+
Previous meeting minutes can be found under http://eavesdrop.openstack.org/meetings/nova_scheduler/
 
 
NOTE: this wiki page should be 'emptied' at the end of each meeting.
 
 
 
=== Next meetings scheduled for: ===
 
* March 20 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170320T140000)
 
* March 27 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170327T140000)
 
* April 3 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170403T140000)
 
 
 
== Agenda for next meeting ==
 
 
 
* Specs & Reviews
 
** TBD
 
 
 
* Bugs
 
** (edleafe) from my functional test work, I noticed that the resource_tracker._allocate_for_instance() silently fails if the resource amounts consumed by an instance violate the inventory constraints. We need to figure out a better way of handling these types of failures.
 
*** Here: https://github.com/openstack/nova/blob/master/nova/compute/resource_tracker.py#L952-L953
 
*** And here: https://github.com/openstack/nova/blob/master/nova/compute/resource_tracker.py#L987-L988
 
*** Failures, if any, are ignored.
 
 
 
* Open discussion
 
** (jroll) I wrote down a rough plan for how we transition ironic flavors, and started thinking about how we move ironic "capabilities" from the ComputeCapabilitiesFilter to placement's traits. Would like quick feedback on the former before I write a spec this week, and will be iterating on the latter to be worked on in queens.
 
*** https://etherpad.openstack.org/p/nova-ironic-flavor-transition-plan
 
** TBD
 
 
 
== Previous meetings ==
 
 
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-03-13-14.00.log.html 2017.03.13]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-03-06-14.00.log.html 2017.03.06]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-02-27-14.00.log.html 2017.02.27]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/ All other meetings are here]
 
 
 
 
 
[[category: compute]]
 
[[category: meetings]]
 

Latest revision as of 14:16, 21 March 2019

The Nova Scheduler meeting is being moved back into the main Nova meeting and the original timeslot will be the Placement meeting. It will be common for nova's use of placement to be a topic at the meeting. Don't worry. It's okay.

Previous meeting minutes can be found under http://eavesdrop.openstack.org/meetings/nova_scheduler/