Good summary, Ed!
Ed Leafe said on Wed, Jun 03, 2015 at 07:53:02AM -0500:
I totally agree the scheduler doesn't have to know anything about
flavors though. We should push them out to request validation in the
Nova API. This can be considered part of cleaning up the scheduler API.
This
Le 03/06/2015 16:02, Nikola Đipanov a écrit :
On 06/03/2015 02:13 PM, John Garbutt wrote:
On 3 June 2015 at 13:53, Ed Leafe e...@leafe.com wrote:
On Jun 2, 2015, at 5:58 AM, Alexis Lee alex...@hp.com wrote:
If you allocate all the memory of a box to high-mem instances, you may
not be
On 06/03/2015 02:13 PM, John Garbutt wrote:
On 3 June 2015 at 13:53, Ed Leafe e...@leafe.com wrote:
On Jun 2, 2015, at 5:58 AM, Alexis Lee alex...@hp.com wrote:
If you allocate all the memory of a box to high-mem instances, you may
not be billing for all the CPU and disk which are now
On Jun 2, 2015, at 5:58 AM, Alexis Lee alex...@hp.com wrote:
If you allocate all the memory of a box to high-mem instances, you may
not be billing for all the CPU and disk which are now unusable. That's
why flavors were introduced, afaik, and it's still a valid need.
So we had a very good
On 3 June 2015 at 13:53, Ed Leafe e...@leafe.com wrote:
On Jun 2, 2015, at 5:58 AM, Alexis Lee alex...@hp.com wrote:
If you allocate all the memory of a box to high-mem instances, you may
not be billing for all the CPU and disk which are now unusable. That's
why flavors were introduced,
Ed Leafe said on Mon, Jun 01, 2015 at 07:40:17AM -0500:
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.
If you allocate all the memory of a box to high-mem instances, you may
not be billing
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
On Jun 1, 2015, at 7:49 AM, Sylvain Bauza sba...@redhat.com wrote:
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
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
