[openstack-dev] Discussion about response value in project-specific-flavor API

unicell unicell at gmail.com
Mon Aug 27 13:09:58 UTC 2012


Thank you for the suggestion, Mark.

Since I've already exposed 'is_public' property on both flavor list and
flavor detail. It seems returning a 404 on on non-private flavor is a
reasonable choice.

And I'll update the patchset to fix. Thanks!

Best Regards,
--
Qiu Yu
http://www.unicell.info


On Mon, Aug 27, 2012 at 8:27 PM, Mark McLoughlin <markmc at redhat.com> wrote:

> On Sat, 2012-08-25 at 11:53 +0800, unicell wrote:
> Hi Folks,
> >
> > In the review comments of my project-specific-flavor blueprint patch,
> > https://review.openstack.org/#/c/11270/
> > Kevin raised a question about response value for public flavor access
> list.
> > And I'd like to posted here for discussion.
> ...
> > # Retrieve public flavor access information
> > stack at precise64:~$ nova flavor-access-list --flavor 1
> > +-----------+-------------+
> > | Flavor_ID | Tenant_ID   |
> > +-----------+-------------+
> > | 1         | ALL TENANTS |
> > +-----------+-------------+
> >
> > Question
> > --
> > For the default public flavor types, is this "ALL TENANTS" an acceptable
> > solution?  It was intended to provide a human readable message for public
> > flaovrs. And, to differentiate from a non-public flavor with no project
> > access configured.
>
> You're trying to model:
>
>   1) A public flavor
>
>   2) A private flavor associated with one or more tenants
>
>   3) A private flavor not associated with any tenants
>
> (2) and (3) can be modelled with a "list of tenants" property, but the
> question is how to model (1) using only a list of tenants
>
> I agree that "ALL TENANTS" isn't acceptable. The obvious solution I see
> is either to expose the "is_public" property or return a 404 if the
> client queries os-flavor-access on a non-private flavor.
>
> Cheers,
> Mark.
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20120827/b7dc6847/attachment.html>


More information about the OpenStack-dev mailing list