|
|
| (229 intermediate revisions by 10 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: ===
| |
| − | * January 9 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170109T140000)
| |
| − | * January 16 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170116T140000)
| |
| − | ** edleafe will not be available
| |
| − | * January 23 2017 1400 UTC, #openstack-meeting-alt (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170123T140000)
| |
| − | | |
| − | == Agenda for next meeting ==
| |
| − | | |
| − | * Specs & Reviews
| |
| − | ** Getting a list of filtered RPs
| |
| − | *** https://review.openstack.org/#/c/392569/
| |
| − | ** Placement Client?
| |
| − | *** Miguelle Lavelle's work: https://github.com/miguellavalle/python-placementclient/tree/adding-grp-support
| |
| − | *** Sylvain's addition of a PlacementClient: https://review.openstack.org/#/c/417111/2
| |
| − | ** Resource Tracker cleanup series:
| |
| − | *** https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/custom-resource-classes
| |
| − | ** Placement Docs
| |
| − | *** https://review.openstack.org/#/c/409340/
| |
| − | | |
| − | * Bugs
| |
| − | ** API not returning aggregate UUIDs: https://bugs.launchpad.net/nova/+bug/1652642
| |
| − | *** Fix: https://review.openstack.org/#/c/415031/
| |
| − | *** Spec: https://review.openstack.org/#/c/415511/
| |
| − | ** Allocation bad input handling and dead code fixing
| |
| − | *** https://review.openstack.org/#/c/416751/
| |
| − | | |
| − | | |
| − | * Open discussion
| |
| − | ** cdent: ''can_host, aggregates in filtering''
| |
| − | *** There's still some confusion (from at least me) on whether the can_host field is relevant when making queries to filter resource providers. Similarly, when requesting resource providers to satisfy a set of resources, we don't (unless I've completely missed it) return resource providers (as compute nodes) that are associated with other resource providers (by aggregate) that can satisfy a resource requirement. Feels like we need to work backwards from a test or use case and see what's missing.
| |
| − | | |
| − | | |
| − | | |
| − | | |
| − | == Previous meetings ==
| |
| − | | |
| − | * [http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-01-02-14.01.log.html 2017.01.02]
| |
| − | * [http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-12-12-14.00.log.html 2016.12.12]
| |
| − | * [http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-12-05-14.00.log.html 2016.12.05]
| |
| − | * [http://eavesdrop.openstack.org/meetings/nova_scheduler/ All other meetings are here]
| |
| − | | |
| − | | |
| − | [[category: compute]]
| |
| − | [[category: meetings]]
| |
