Le 01/06/2015 14:40, Ed Leafe a écrit :
Several of the discussions at Vancouver got me thinking about what seems to me
to be a fundamental mis-match in Nova: the way we think about resources, and
how we handle requesting/claiming them. I wrote down my initial thoughts
(http://blog.leafe.com/rethinking-resources/), but as many of you took the week
off after the summit, I waited until today to start a ML discussion.
Nova started when "the cloud" was pretty much the VPS model of on-demand compute: you had
big powerful servers that you wanted to virtualize into several smaller chunks, and you did that
with hypervisors on those servers. Along with this came the concept of "flavors", which
were the available portions of the overall server you could request.
Over the years, though, that model has become just one of many (bare metal,
NUMA, etc.), yet our internal model still tries to force everything into the
flavor world. And with the advent of technologies such as LXD, it seems likely
that the VPS model will begin to fade away and replaced by more efficient ways
to share compute.
We need to update our concept of a resource internally in Nova, both in the DB
and in code, and stop thinking that every request should have a flavor. This is
also the single biggest blocker in separating the Scheduler into a separate
service that can be used to allocate resources in Cinder and Neutron, too,
because we've tied it exclusively to the concept of a VPS resource. I'd like to
start a discussion and get people's opinions on this. I have some ideas, of
course, but I know that as these are not simple issues, getting input from many
different perspectives is going to lead to a better approach. So: what do you
think would be a better way to represent resources, as well as a better way to
represent a request for some of those resources?
-- Ed Leafe
Long story short :
https://blueprints.launchpad.net/nova/+spec/resource-objects
Until we get this, it's difficult to discuss on different resources
within Nova. Let's work by small steps and provide a versioned resource
system before discussing on how other projects could add more resources
to Nova.
-Sylvain
__________________________________________________________________________
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
__________________________________________________________________________
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
