Difference between revisions of "Meetings/NovaScheduler"
< Meetings
(→Agenda for next meeting) |
m (→Agenda for next meeting) |
||
Line 16: | Line 16: | ||
* Specs & Reviews | * Specs & Reviews | ||
** Reviews | ** Reviews | ||
− | *** Provider Tree series, starting with: https://review.openstack.org/#/c/ | + | *** Provider Tree series, starting with: https://review.openstack.org/#/c/537648/ |
*** Nested RP traits selection: https://review.openstack.org/#/c/531899/ | *** Nested RP traits selection: https://review.openstack.org/#/c/531899/ | ||
− | |||
*** Granular resource requests review: https://review.openstack.org/#/c/517757/ | *** Granular resource requests review: https://review.openstack.org/#/c/517757/ | ||
*** Remove microversion fallback: https://review.openstack.org/#/c/528794/ | *** Remove microversion fallback: https://review.openstack.org/#/c/528794/ |
Revision as of 13:52, 5 February 2018
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:
- February 5 2018 1400 UTC, #openstack-meeting-alt
- February 12 2018 1400 UTC, #openstack-meeting-alt
- February 19 2018 1400 UTC, #openstack-meeting-alt
Agenda for next meeting
- Specs & Reviews
- Reviews
- Provider Tree series, starting with: https://review.openstack.org/#/c/537648/
- Nested RP traits selection: https://review.openstack.org/#/c/531899/
- Granular resource requests review: https://review.openstack.org/#/c/517757/
- Remove microversion fallback: https://review.openstack.org/#/c/528794/
- Use alternate hosts for resize: https://review.openstack.org/#/c/537614/
- Reviews
- Bugs
- Placement bugs
- Open discussion
- Should allocations fail if there is a generation mis-match for a provider, even if the provider still has sufficient available inventory?
- See https://bugs.launchpad.net/nova/+bug/1719933
- Could we perhaps increment the generation on a successful allocation even if the generation is older?
- Should allocations fail if there is a generation mis-match for a provider, even if the provider still has sufficient available inventory?