Hi!
Comments inline.
On 20/05/14 21:58, "Zane Bitter" wrote:
>On 20/05/14 12:17, Jay Pipes wrote:
>> Hi Zane, sorry for the delayed response. Comments inline.
>>
>> You are assuming a public cloud provider use case above. As much as I
>> tend to focus on the utility cloud model, where the incent
On 20/05/14 12:17, Jay Pipes wrote:
Hi Zane, sorry for the delayed response. Comments inline.
On 05/06/2014 09:09 PM, Zane Bitter wrote:
On 05/05/14 13:40, Solly Ross wrote:
One thing that I was discussing with @jaypipes and @dansmith over
on IRC was the possibility of breaking flavors down in
Hi Zane, sorry for the delayed response. Comments inline.
On 05/06/2014 09:09 PM, Zane Bitter wrote:
On 05/05/14 13:40, Solly Ross wrote:
One thing that I was discussing with @jaypipes and @dansmith over
on IRC was the possibility of breaking flavors down into separate
components -- i.e have a
>
> This is why there is a distinction between properties set on images
> vs properties set on flavours. Image properties, which a normal user
> can set, are restricted to aspects of the VM which don't involve
> consumption of compute host resources. Flavour properties, which
> only a user with 'f
ack Development
> Mailing List (not for usage questions)"
>
> Sent: Thursday, May 8, 2014 10:51:47 AM
> Subject: Re: [openstack-dev] [Nova] [Heat] Custom Nova Flavor creation
> through Heat (pt.2)
>
> The way I was thinking this would work would be to allow "fla
Daniel P. Berrange"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Thursday, May 8, 2014 5:08:32 AM
> Subject: Re: [openstack-dev] [Nova] [Heat] Custom Nova Flavor creation
> through Heat (pt.2)
>
> On Mon, May 05, 2014 at 01:40:
On Thu, May 08, 2014 at 11:22:38AM +0100, Daniel P. Berrange wrote:
> On Mon, May 05, 2014 at 07:40:08PM +, Dimitri Mazmanov wrote:
> > This is good! Is there a blueprint describing this idea? Or any plans
> > describing it in a blueprint?
> > Would happily share the work.
> >
> > Should we mi
On Mon, May 05, 2014 at 07:40:08PM +, Dimitri Mazmanov wrote:
> This is good! Is there a blueprint describing this idea? Or any plans
> describing it in a blueprint?
> Would happily share the work.
>
> Should we mix it with flavors in horizon though? I¹m thinking of having a
> separate ³Resour
On Mon, May 05, 2014 at 01:40:43PM -0400, Solly Ross wrote:
> One thing that I was discussing with @jaypipes and @dansmith over
> on IRC was the possibility of breaking flavors down into separate
> components -- i.e have a disk flavor, a CPU flavor, and a RAM flavor.
> This way, you still get the c
(response inline)
- Original Message -
> From: "Zane Bitter"
> To: openstack-dev@lists.openstack.org
> Sent: Tuesday, May 6, 2014 9:09:09 PM
> Subject: Re: [openstack-dev] [Nova] [Heat] Custom Nova Flavor creation
> through Heat (pt.2)
>
> On 05/05/14 1
On 05/05/14 13:40, Solly Ross wrote:
One thing that I was discussing with @jaypipes and @dansmith over
on IRC was the possibility of breaking flavors down into separate
components -- i.e have a disk flavor, a CPU flavor, and a RAM flavor.
This way, you still get the control of the size of your bu
On Mon, May 05, 2014 at 07:40:08PM +, Dimitri Mazmanov wrote:
> This is good! Is there a blueprint describing this idea? Or any plans
> describing it in a blueprint?
> Would happily share the work.
>
> Should we mix it with flavors in horizon though? I¹m thinking of having a
> separate ³Resour
> -Original Message-
> From: Solly Ross [mailto:sr...@redhat.com]
> Sent: Tuesday, May 06, 2014 10:16 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] [Heat] Custom Nova Flavor creation
> through Heat (pt.2)
&
ng List (not for usage questions)"
>
>Sent: Monday, May 5, 2014 3:40:08 PM
>Subject: Re: [openstack-dev] [Nova] [Heat] Custom Nova Flavor creation
>through Heat (pt.2)
>
>This is good! Is there a blueprint describing this idea? Or any plans
>describing it in a blueprint
t for usage questions)"
Sent: Monday, May 5, 2014 3:40:08 PM
Subject: Re: [openstack-dev] [Nova] [Heat] Custom Nova Flavor creation through
Heat (pt.2)
This is good! Is there a blueprint describing this idea? Or any plans
describing it in a blueprint?
Would happily share the work.
Shoul
This is good! Is there a blueprint describing this idea? Or any plans
describing it in a blueprint?
Would happily share the work.
Should we mix it with flavors in horizon though? I¹m thinking of having a
separate ³Resources² page,
wherein the user can ³define² resources. I¹m not a UX expert though
On 05/05/2014 12:18 PM, Chris Friesen wrote:
As a simplifying view you could keep the existing flavors which group
all of them, while still allowing instances to specify each one
separately if desired.
Also, if we're allowing the cpu/memory/disk to be specified
independently at instance boot
On 05/05/2014 11:40 AM, Solly Ross wrote:
One thing that I was discussing with @jaypipes and @dansmith over
on IRC was the possibility of breaking flavors down into separate
components -- i.e have a disk flavor, a CPU flavor, and a RAM flavor.
This way, you still get the control of the size of yo
On 05/05/2014 10:51 AM, Steve Gordon wrote:
In addition extra specifications may denote the passthrough of additional
devices, adding another dimension. This seems likely to be the case in the use
case outlined in the original thread [1].
Thanks,
Steve
[1] http://lists.openstack.org/piperma
/#/c/91444/).
- Original Message -
From: "Dimitri Mazmanov"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, May 5, 2014 1:20:09 PM
Subject: Re: [openstack-dev] [Nova] [Heat] Custom Nova Flavor creation through
Heat (pt.2)
I guess I
t (not for usage questions)"
>
>Sent: Monday, May 5, 2014 2:18:21 AM
>Subject: Re: [openstack-dev] [Nova][Heat] Custom Nova Flavor creation
>through Heat (pt.2)
>
>> Having project-scoped flavors will rid us of the identified issues, and
>>will allow a more fine-grain
Excerpts from Solly Ross's message of 2014-05-05 10:01:12 -0700:
> If you actually have 64 flavors, though, and it's overwhelming
> your users, it would be pretty trivial to implement a "flavor
> recommender" where you input your requirements and it pops out
> the nearest flavor. That being said,
Re: [openstack-dev] [Nova][Heat] Custom Nova Flavor creation through
Heat (pt.2)
Excerpts from Solly Ross's message of 2014-05-05 08:23:41 -0700:
> Just to expand a bit on this, flavors are supposed to be the lowest level of
> granularity,
> and the general idea is to round
- Original Message -
> Excerpts from Solly Ross's message of 2014-05-05 08:23:41 -0700:
> > Just to expand a bit on this, flavors are supposed to be the lowest level
> > of granularity,
> > and the general idea is to round to the nearest flavor (so if you have a VM
> > that requires
> > 3GB
Excerpts from Solly Ross's message of 2014-05-05 08:23:41 -0700:
> Just to expand a bit on this, flavors are supposed to be the lowest level of
> granularity,
> and the general idea is to round to the nearest flavor (so if you have a VM
> that requires
> 3GB of RAM, go with a 4GB flavor). Hence,
s that are extremely over-allocated).
Best Regards,
Solly Ross
- Original Message -
From: "Serg Melikyan"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, May 5, 2014 2:18:21 AM
Subject: Re: [openstack-dev] [Nova][Heat] Custom Nova F
>Having project-scoped flavors will rid us of the identified issues, and
will allow a more fine-grained way of managing physical resources.
Flavors concept was introduced in clouds to solve issue with effective
physical resource usage: 8Gb physical memory can be effectively splitted to
two m2.my_s
This topic has already been discussed last year and a use-case was described
(see [1]).
Here's a Heat blueprint for a new OS::Nova::Flavor resource: [2].
Several issues have been brought up after posting my implementation for review
[3], all related to how flavors are defined/implemented in nova:
28 matches
Mail list logo
