Open Stack

On 05/29/2013 03:11 AM, Sunny wrote:
> Hi Gabriel Hurley,
>     I try to finish the blueprint "define-flavor-for-project". Please
> refer to: https://review.openstack.org/26822
>     However, in the process of change, for this comment "Shouldn't a
> project member be able to manage flavors for their own project? The
> admin functionality here is good, but it needs a counterpart in the
> project dashboard", I have some issues and want to listen to your advice.
>     First, there are no nova api to support querying "private" flavors
> by tenant. As mentioned in function "_list_by_tenant()" of
> "python-novaclient/novaclient/v1_1/flavor_access.py", so far, nova can't
> support querying flavors by tenant. So, I add Russell Bryant to the
> recipientlist.

You are correct, AFAIK.

This has come up before, sort of.  While discussing things we need to
better support homogeneous environments (a nova deployment with
baremetal and virt, for example), one of the things we wanted was the
ability to define flavors that are only accessible by a certain tenant.
 In that case, it will still only be managed by an administrator.
Optionally allowing tenants to manage their own flavors seems like a
logical extension to that.

>     Second, after adding "Flavors" page under "Project" tab, there will
> have two kinds of private flavor. One is created by administrator, which
> can be shared by multiple projects; Another is created by  members,
> which can only be owned by the current project. For administrators, they
> can delete the two kinds of flavors, but for members, they can only
> delete the flavors which only belong to the current project. Right?


-- 
Russell Bryant