Difference between revisions of "Meetings/NovaScheduler"
< Meetings
(→Agenda for next meeting) |
|||
| Line 24: | Line 24: | ||
* Open discussion | * 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 | ** TBD | ||
Revision as of 12:51, 20 March 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:
- 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.
- (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.
- 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.
- TBD
