Jump to: navigation, search

Difference between revisions of "Meetings/NovaScheduler"

(Agenda for next meeting)
 
(137 intermediate revisions by 6 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: ===
 
* No meetings December 25 and January 1
 
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20180108T140000 January 8 2018 1400 UTC], #openstack-meeting-alt
 
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20180115T140000 January 15 2018 1400 UTC], #openstack-meeting-alt
 
 
 
== Agenda for next meeting ==
 
 
 
* Specs & Reviews
 
** Reviews
 
*** Nested RPs:
 
**** ComputeDriver.update_provider_tree() series starting with: https://review.openstack.org/#/c/521685/ (efried) (See open discussion topic)
 
**** Nested affordance in GET /allocation_candidates (jaypipes)
 
**** Granular resource requests (efried): https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/granular-resource-requests (waiting for ^^)
 
*** Alternate hosts (edleafe):
 
**** Series now starts with test case patch https://review.openstack.org/#/c/531022/
 
**** Revealed bug: https://bugs.launchpad.net/nova/+bug/1741125
 
 
 
* Bugs
 
** Placement bugs
 
*** https://bugs.launchpad.net/nova/+bugs?field.tag=placement
 
 
 
* Open discussion
 
** Using /allocation_candidates?limit= from nova-side, should we? how?
 
** sharing providers in ProviderTree: https://review.openstack.org/#/c/526539/
 
*** If sharing providers are managed by compute nodes, how does coordination work?  Answer: careful handling of conflicts
 
**** Generation support needed for PUT /rp/{uuid}/aggregates
 
**** Sensible reGET/retry on 409s
 
*** Can we centralize all that logic in the report client and have it work for all cases, or do virt drivers need more control?  (Related to below.)
 
** Why can't (in-tree) virt drivers talk to placement?  See conversation seeds in patch-level comments on https://review.openstack.org/#/c/526539/7
 
 
 
== Previous meetings ==
 
 
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-12-18-14.00.log.html 2017.12.18]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-12-11-14.00.log.html 2017.12.11]
 
* [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-12-04-14.00.log.html 2017.12.04]
 
* [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/