... why? It strikes me as a rather shallow business decision to limit the number of users or projects in a system, as neither are actually cost-consuming resources. On Thu, Jan 23, 2014 at 6:43 AM, Matthieu Huin <matthieu.huin at enovance.com>wrote: > Hello, > > I'd be interested in opinions and feedback on the following blueprint: > https://blueprints.launchpad.net/keystone/+spec/tenants-users-quotas > > The idea is to add a mechanism preventing the creation of users or > projects once a quota per domain is met. I believe this could be > interesting for cloud providers who delegate administrative rights under > domains to their customers. > > I'd like to hear the community's thoughts on this, especially in terms of > viability. > > Many thanks, > > Matthieu Huin > > mhu at enovance.com > http://www.enovance.com > eNovance SaS - 10 rue de la Victoire 75009 Paris - France > > > _______________________________________________ > 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/20140123/df6bbfb9/attachment.html>