On 03/20/2017 04:24 PM, Blair Bethwaite wrote:
For me an interesting question to know the answer to here would be at what point
you have to stop resource sharing to guarantee your performance promises/SLAs
(disregarding memory over-provisioning). My gut says that unless you are also
doing all th
Hi Chris,
On 17 Mar. 2017 15:24, "Chris Friesen" wrote:
On 03/16/2017 07:06 PM, Blair Bethwaite wrote:
Statement: breaks bin packing / have to match flavor dimensions to hardware
> dimensions.
> Comment: neither of these ring true to me given that most operators tend to
> agree that memory is t
On 03/16/2017 07:06 PM, Blair Bethwaite wrote:
Statement: breaks bin packing / have to match flavor dimensions to hardware
dimensions.
Comment: neither of these ring true to me given that most operators tend to
agree that memory is there first constraining resource dimension and it is
difficult
*From:* Adam Lawson [mailto:alaw...@aqorn.com]
> *Sent:* Thursday, March 16, 2017 5:57 PM
> *To:* Jonathan D. Proulx
> *Cc:* OpenStack Operators
> *Subject:* Re: [Openstack-operators] Flavors
>
>
>
> One way I know some providers work around this when using OpenStack is by
: Jonathan D. Proulx
Cc: OpenStack Operators
Subject: Re: [Openstack-operators] Flavors
One way I know some providers work around this when using OpenStack is by
fronting the VM request with some code in the web server that checks if the
requested spec has an existing flavor. if so, use the flavor
One way I know some providers work around this when using OpenStack is by
fronting the VM request with some code in the web server that checks if the
requested spec has an existing flavor. if so, use the flavor, if not, use
an admin account that creates a new flavor and assign use it for that user
I have always hated flavors and so do many of my users.
On Wed, Mar 15, 2017 at 03:22:48PM -0700, James Downs wrote:
:On Wed, Mar 15, 2017 at 10:10:00PM +, Fox, Kevin M wrote:
:> I think the really short answer is something like: It greatly simplifies
scheduling and billing.
:
:The real answ
>> handle those large ram VM’s?
>>
>>
>>
>> ___
>>
>> Kris Lindgren
>>
>> Senior Linux Systems Engineer
>>
>> GoDaddy
>>
>>
>>
>> *From: *Matthew Kauf
> GoDaddy
>
>
>
> *From: *Matthew Kaufman
> *Date: *Wednesday, March 15, 2017 at 5:42 PM
> *To: *"Fox, Kevin M"
> *Cc: *OpenStack Operators
> *Subject: *Re: [Openstack-operators] Flavors
>
>
>
> Screw the short answer -- that is annoying to r
ed to handle those
> large ram VM’s?
>
> ___
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
> From: Matthew Kaufman
> Date: Wednesday, March 15, 2017 at 5:42 PM
> To: "Fox, Kevin M&qu
Operators
Subject: Re: [Openstack-operators] Flavors
Screw the short answer -- that is annoying to read, and it doesn't simplify
BILLING from a CapEx/OpEx perspective, so please - wtf?
Anyway, Vladimir - I love your question and have always wanted the same thing.
On Wed, Mar 15, 2017
ly short answer is something like: It greatly simplifies
> scheduling and billing.
>
> --
> *From:* Vladimir Prokofev [v...@prokofev.me]
> *Sent:* Wednesday, March 15, 2017 2:41 PM
> *To:* OpenStack Operators
> *Subject:* [Openstack-operators] Flavor
Wednesday, March 15, 2017 5:10 PM
To: Vladimir Prokofev; OpenStack Operators
Subject: Re: [Openstack-operators] Flavors
I think the really short answer is something like: It greatly simplifies
scheduling and billing.
From: Vladimir Prokofev [v...@prokofev.me]
Sent:
On Wed, Mar 15, 2017 at 10:10:00PM +, Fox, Kevin M wrote:
> I think the really short answer is something like: It greatly simplifies
> scheduling and billing.
The real answer is that once you buy hardware, it's in a fixed radio of
CPU/Ram/Disk/IOPS, etc.
In order to use the hardware effecti
I think the really short answer is something like: It greatly simplifies
scheduling and billing.
From: Vladimir Prokofev [v...@prokofev.me]
Sent: Wednesday, March 15, 2017 2:41 PM
To: OpenStack Operators
Subject: [Openstack-operators] Flavors
A question of
A question of curiosity - why do we even need flavors?
I do realise that we need a way to provide instance configuration, but why
use such a rigid construction? Wouldn't it be more flexible to provide
instance configuration as a set of parameters(metadata), and if you need
some presets - well, use
16 matches
Mail list logo
