Open Stack

Hi Folks,

I'm looking at couple use cases where I'd really like to have additional per-tenant data supplied from keystone.

The first case is to make the current quota-classes extension in Nova usable - this provides a much better way to manage quotas, but relies on the quota_class being set in the context.

The second case is to prove a per-tenant default availability zone - having a default makes sense in some cases, but having the same default for all tenants (which is what the current config option gives) can be an issue from a load balancing perspective.

I guess I could just do all of this via the roles in current keystone (i.e. define a role with a name like "quota_class:xxx" and "default_az:az1"), as these seem to be  in effect arbitrary properties of a tenant as far as keystone is concerned, but I'm wondering if there shouldn't be some more general way of adding key-value attributes to a tenant.

Thoughts ?

Phil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130130/70e2f31e/attachment.html>