Re: [Openstack] [OpenStack][Keystone] Blueprint to store quota data in Keystone

You raise some excellent points here. I've been focused on aligning the CLI with REST methods one-to-one and staying consistent with the other subcommands but there's more to consider. It would really suck to be an admin and have to guess at whether or not a tenant already had a quota set so you c

Re: [Openstack] [OpenStack][Keystone] Blueprint to store quota data in Keystone

Hi Everett, > Secondly, with regard to quota-create and quota-update, is there a huge >> difference between the two besides one would ultimately do an "insert" and >> one would do an "update"? If that is the only difference, could the two be >> combined into a single "quota-set" subcommand? >> >

Re: [Openstack] [OpenStack][Keystone] Blueprint to store quota data in Keystone

On Fri, May 11, 2012 at 9:07 AM, Joe Topjian wrote: > > With regard to your "dot" notation, couldn't multiple --quota args be > used? For example: > > keystone quota-create --quota nova.ram=102400 --quota nova.instances=20 > --quota swift.total=1073741824 > Hmmmthis would be possible with n

Re: [Openstack] [OpenStack][Keystone] Blueprint to store quota data in Keystone

On May 10, 2012, at 12:55 PM, Everett Toews wrote: > Hi All, > > I've started a blueprint and spec to store quota data in Keystone. Please > have a look if you're interested and any feedback is welcome. > > Of course, writing up the spec brought up number of questions for me. You can > find

Re: [Openstack] [OpenStack][Keystone] Blueprint to store quota data in Keystone

Hi Everett, > 1. For the keystone CLI I'm proposing using JSON for batch create, update, > and delete of quotas. I don't believe this is done anywhere else in > OpenStack. Good idea? Bad idea? > My plan is to go with the JSON. > IMO, using JSON on the command line is pretty unconventional with r

[Openstack] [OpenStack][Keystone] Blueprint to store quota data in Keystone

Hi All, I've started a blueprintand spec to store quota data in Keystone. Please have a look if you're interested and any feedback is welcome. Of course, writing up the spec broug