Difference between revisions of "Meetings/NovaScheduler"
< Meetings
(→Previous meetings) |
(→Agenda for next meeting) |
||
| Line 23: | Line 23: | ||
*** Separating qualitative requirements from quantitative in a request - https://review.openstack.org/313784 | *** Separating qualitative requirements from quantitative in a request - https://review.openstack.org/313784 | ||
* Open discussion | * Open discussion | ||
| − | ** | + | ** Other services directly accessing the Scheduler and/or request database |
| + | *** Watcher has a proposed spec: https://review.openstack.org/#/c/329873 | ||
| + | *** We need to clarify if this is an approach we want to actively discourage | ||
== Previous meetings == | == Previous meetings == | ||
Revision as of 13:33, 24 June 2016
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.
Agenda for next meeting
Next meetings scheduled for:
- June 27 2016 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160627T140000)
- July 4, 2016 - NO MEETING (US holiday)
- July 11 2016 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160711T140000)
Here is the agenda for the next meeting:
- Specs & Reviews
- TBD
- Mid-cycle
- Topics to discuss (add yours to the list below, with URLs if applicable)
- Accepting multiple hsots for live migration - https://review.openstack.org/276840
- Separating qualitative requirements from quantitative in a request - https://review.openstack.org/313784
- Topics to discuss (add yours to the list below, with URLs if applicable)
- Open discussion
- Other services directly accessing the Scheduler and/or request database
- Watcher has a proposed spec: https://review.openstack.org/#/c/329873
- We need to clarify if this is an approach we want to actively discourage
- Other services directly accessing the Scheduler and/or request database
