[Openstack-operators] Confused by user management
lorin at nimbisservices.com
Wed Aug 15 02:03:48 UTC 2012
On Aug 14, 2012, at 9:30 PM, Samuel Winchenbach <swinchen at gmail.com> wrote:
> H,, interesting. Using quota-update I get the following:
> error: argument <subcommand>: invalid choice: 'quota-update'
This is what happens when I try it (I believe this is the latext version of python-novaclient from pypi)
$ nova quota-update
usage: nova quota-update [--instances <instances>] [--cores <cores>]
[--ram <ram>] [--volumes <volumes>]
error: too few arguments
Try 'nova help quota-update' for more information.
Lead Architect - Cloud Services
Nimbis Services, Inc.
> On Tue, Aug 14, 2012 at 9:06 PM, Lorin Hochstein
> <lorin at nimbisservices.com> wrote:
>> On Aug 14, 2012, at 12:36 PM, Jonathan Proulx <jon at jonproulx.com> wrote:
>> On Tue, Aug 14, 2012 at 12:27 PM, Lorin Hochstein
>> <lorin at nimbisservices.com> wrote:
>> All management of users, tenants and service endpoints should be done using
>> the "keystone" client. Don't use "nova-manage user *", those commands
>> predate keystone and are now obsolete.
>> I do think you will still need 'nova-manage project quota ' though
>> creating the users and tenants through keystone. If that's not
>> current info I'd love to know the "right way"
>> Apparently, you can also do "nova quota-update" to set project-specific
>> quotas. There's an outstanding doc bug to capture this:
>> Take care,
>> Lorin Hochstein
>> Lead Architect - Cloud Services
>> Nimbis Services, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators