Open Stack

Hi Ray,

On 3 April 2013 19:41, Ray Sun <qsun01185 at cienet.com.cn> wrote:
>
> I am not sure this is the right place to discuss implementation. My colleague and I want to implement this feature:
> https://blueprints.launchpad.net/horizon/+spec/define-flavor-for-project

Great!

> Currently, we have two ways:
> 1. We want to add a "public checkbox" in flavor editing page, and add a new step called "Flavor Access" to allow user to select the project for accessing the flavor. And there's no relationship between the "public checkbox" and "flavor access". That's means when user check the "public checkbox", it's useless to do any operation on "Flavor Access".
> 2. Only add a "Flavor Access" Step at flavor editing page, and by default, we will choose all the projects for the specific flavor, so flavor's is_public will be always true if user don't do any operation in the database. If user remove one project from "Access List", we will update the flavor to private and update the project access list.

Best to make it obvious to the user what is happening. You might want
to consider putting the public checkbox on the Flavor Access step,
since that's where it seems to belong. In any case, make sure you
disable the other Flavor Access controls when it is checked. And make
it checked by default to retain current behaviour.

Have a look at the Project/Edit Users control in the Admin dashboard.
You should be able to reuse this for the Flavor Access page. Let me
know if you have any questions.

Cheers,
Kieran


>
>
> Please help. Thanks.
>
> - Ray
> Best Regards
>
> CIeNET Technologies (Beijing) Co., Ltd
> Technical Manager
> Email: qsun01185 at cienet.com.cn
> Office Phone: +86-01081470088-7079
> Mobile Phone: +86-13581988291
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>