I noticed there were some changes to the way we used openstack quotas today. So I had to do it the manual way! Please note that this can only be done thru the Admin API function, so if you are a Rackspace customer you would need to reach out to us to do this, unless you ran your own openstack or devstack implementation in-house.
Here is how I achieved it:
supernova {environment} {action} --option {number} {customer_ID}
supernova lon quota-update --instances 250 10010101
There is a lot of different commands available, use nova help to get more detail
supernova lon help quota-update [SUPERNOVA] Running nova against lon... usage: nova quota-update [--user] [--instances ] [--cores ] [--ram ] [--floating-ips ] [--fixed-ips ] [--metadata-items ] [--injected-files ] [--injected-file-content-bytes ] [--injected-file-path-bytes ] [--key-pairs ] [--security-groups ] [--security-group-rules ] [--server-groups ] [--server-group-members ] [--force] Update the quotas for a tenant/user. Positional arguments: ID of tenant to set the quotas for. Optional arguments: --user ID of user to set the quotas for. --instances New value for the "instances" quota. --cores New value for the "cores" quota. --ram New value for the "ram" quota. --floating-ips New value for the "floating-ips" quota. --fixed-ips New value for the "fixed-ips" quota. --metadata-items New value for the "metadata-items" quota. --injected-files New value for the "injected-files" quota. --injected-file-content-bytes New value for the "injected-file-content- bytes" quota. --injected-file-path-bytes New value for the "injected-file-path-bytes" quota. --key-pairs New value for the "key-pairs" quota. --security-groups New value for the "security-groups" quota. --security-group-rules New value for the "security-group-rules" quota. --server-groups New value for the "server-groups" quota. --server-group-members New value for the "server-group-members" quota. --force Whether force update the quota even if the already used and reserved exceeds the new quota.