On Aug 11, 2016, at 5:29 PM, John Dickinson <[email protected]> wrote: >> I will let Jay speak for himself (as if I could somehow prevent that!), but >> the intent here is that this won’t be for Nova specifically; it is targeted >> primarily for the forthcoming placement service (you might know it as the >> scheduler). The goal is to have a standard way of representing *qualitative* >> aspects of resources. So while we are not actively trying to make this a >> placement engine for all OpenStack services yet, the goal is to not be >> Nova-specific, so that once we have this up and running, we can offer it as >> a general placement service for any other project that has such needs. > > Sounds great! How can I get involved with the new general purpose placement > scheduler engine and share Swift's requirements?
The main work being done now is on moving Nova from hard-coded CPU, disk, etc., to use Resource Provider classes instead. You can see the current work at https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/generic-resource-pools You can also join the scheduler subteam meeting Mondays at 1400 UTC in @openstack-meeting-alt, where we discuss our current efforts. If you have a specific question or topic to bring up, add it to the meeting agenda at https://wiki.openstack.org/wiki/Meetings/NovaScheduler. -- Ed Leafe __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
