Is there anyway we can make sure that blueprints have a lot more in them. That's great for a introduction but I'd really like to see design plans, how it was done, the architecture, the api.... Is there a "recommendation" for this (which really should be enforced)? I think I remember seeing one before but not quite sure... -Josh On 3/16/12 2:56 PM, "Kevin L. Mitchell" <kevin.mitchell at rackspace.com> wrote: I wanted to let everyone know about a quota classes blueprint I've submitted; you can find the details here: * https://blueprints.launchpad.net/nova/+spec/quota-classes * http://wiki.openstack.org/QuotaClass I've already implemented this blueprint and pushed to Gerrit, but have it -2'd for right now since we haven't opened trunk yet for Folsom. If you'd like to have a look at it, the relevant changes are: * Nova: https://review.openstack.org/#change,5298 * Nova client: https://review.openstack.org/#change,5299 -- Kevin L. Mitchell <kevin.mitchell at rackspace.com> _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack at lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120316/8666c508/attachment.html>