<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><br></div></div><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><br></span></div><div><div>On Aug 14, 2012, at 9:30 PM, Samuel Winchenbach <<a href="mailto:swinchen@gmail.com">swinchen@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">H,, interesting.  Using quota-update I get the following:<br><br>error: argument <subcommand>: invalid choice: 'quota-update'<br><br><br></blockquote><div><div><div><br></div><div>This is what happens when I try it (I believe this is the latext version of python-novaclient from pypi)</div><div><br></div><div>$ nova quota-update</div><div>usage: nova quota-update [--instances <instances>] [--cores <cores>]</div><div>                         [--ram <ram>] [--volumes <volumes>]</div><div>                         [--gigabytes <gigabytes>]</div><div>                         [--floating-ips <floating_ips>]</div><div>                         [--metadata-items <metadata_items>]</div><div>                         [--injected-files <injected_files>]</div><div>                         [--injected-file-content-bytes <injected_file_content_bytes>]</div><div>                         <tenant_id></div><div>error: too few arguments</div><div>Try 'nova help quota-update' for more information.</div></div><div><br></div><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Take care,</div><div><br></div><div>Lorin</div><div>--</div><div>Lorin Hochstein</div><div>Lead Architect - Cloud Services</div><div>Nimbis Services, Inc.</div><div><a href="https://www.nimbisservices.com/">www.nimbisservices.com</a></div><div><br></div></div></span></div></span></div></div><br><div><br></div><br><blockquote type="cite"><br>On Tue, Aug 14, 2012 at 9:06 PM, Lorin Hochstein<br><<a href="mailto:lorin@nimbisservices.com">lorin@nimbisservices.com</a>> wrote:<br><blockquote type="cite"><br>On Aug 14, 2012, at 12:36 PM, Jonathan Proulx <<a href="mailto:jon@jonproulx.com">jon@jonproulx.com</a>> wrote:<br><br>On Tue, Aug 14, 2012 at 12:27 PM, Lorin Hochstein<br><<a href="mailto:lorin@nimbisservices.com">lorin@nimbisservices.com</a>> wrote:<br><br>All management of users, tenants and service endpoints should be done using<br>the "keystone" client. Don't use "nova-manage user *", those commands<br>predate keystone and are now obsolete.<br><br><br>I do think you will still need 'nova-manage project quota '  though<br>creating the users and tenants through keystone.   If that's not<br>current info I'd love to know the "right way"<br><br><br>Apparently, you can also do "nova quota-update" to set project-specific<br>quotas. There's an outstanding doc bug to capture this:<br><br><a href="https://bugs.launchpad.net/openstack-manuals/+bug/979941">https://bugs.launchpad.net/openstack-manuals/+bug/979941</a><br><br><br>Take care,<br><br>Lorin<br>--<br>Lorin Hochstein<br>Lead Architect - Cloud Services<br>Nimbis Services, Inc.<br>www.nimbisservices.com<br><br><br><br><br></blockquote></blockquote></div><br></body></html>