On Wed, 16 Dec 2015, melanie witt wrote:
I’d rather we provided something like a more generic “Resource
View API” in Nova that allows baremetal/container/clustered
hypervisor environments to report resources via a REST API, and
scheduling would occur based on the resources table (instead of having
resource trackers). Each environment reporting resources would provide
corresponding in-tree Nova scheduler filters that know what to do with
resources related to them. Then scheduling would select a resource and
lookup the compute host responsible for that resource, and nova-
compute would delegate the chosen resource to, for example, Ironic.
That ^ makes me think of this: https://review.openstack.org/#/c/253187/
Seem to be in at least similar veins.
--
Chris Dent (�s°□°)�s�喋擤ォ� http://anticdent.org/
freenode: cdent tw: @anticdent
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
