Open Stack

Hi Solly,

On 06/05/14 19:16, "Solly Ross" <sross at redhat.com> wrote:

>For your first question, I'll probably create a BP sometime today.

Great. Thanks. Happy to help with implementation.

>
>For your second question, allowing tenants to create flavors
>prevents one of the main parts of the flavor idea from working --
>having flavors that nicely fit together to prevent "wasted" host
>resources.  For instance suppose the normal system flavors used
>memory in powers of 2GB (2, 4, 8, 16, 32).  Now suppose someone
>came in, created a private flavor that used 3GB of RAM.  We now
>have 1GB of RAM that can never be used, unless someone decides
>to come along and create a 1GB flavor (actually, since RAM has
>even more granularity than that, you could have someone specify
>that they wanted 1.34GB of RAM, for instance, and then you have
>all sorts of weird stuff going on).

When I said "create custom flavor" I never meant allowing the users such
nonsense as specifying 1.34GB of RAM (this can be controlled by having
constraints). Although some can be very meticulous :)
Still an issue?
My basic idea was to let the users think in terms of physical resources
and based on that let them create the configuration they need (if they
don’t find the right flavor in the global list).

>
>Best Regards,
>Solly Ross
>
>----- Original Message -----
>From: "Dimitri Mazmanov" <dimitri.mazmanov at ericsson.com>
>To: "OpenStack Development Mailing List (not for usage questions)"
><openstack-dev at lists.openstack.org>
>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.
>
>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.
>
>But let me come back to the project-scoped flavor creation issues.
>Why do you think it¹s such a bad idea to let tenants create flavors for
>their project specific needs?
>
>I¹ll refer again to the Steve Hardy¹s proposal:
>- Normal user : Can create a private flavor in a tenant where they
>  have the Member role (invisible to any other users)
>- Tenant Admin user : Can create public flavors in the tenants where they
>  have the admin role (visible to all users in the tenant)
>- Domain admin user : Can create public flavors in the domains where they
>  have the admin role (visible to all users in all tenants in that domain)
>
>
>> If you actually have 64 flavors, though, and it's overwhelming
>> your users, ...
>
>The users won¹t see all 64 flavor, only those they have defined and
>public.
>______________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev