havana: nova adds per-project-user quotas

[Tom Fifield]

https://review.openstack.org/28232 adds new feature to nova: per-project-user quotas

    quota_instances, quota_cores, quota_ram, quota_key_pairs and
    quota_security_groups are supported per user.

    Add CRUD methods for project user quotas API. DocImpact
     - Shows quotas for a user.
       GET v2/{tenant_id}/os-quota-sets/{tenant_id}?user_id={user_id}
     - Updates quotas for a user.
       POST v2/{tenant_id}/os-quota-sets/{tenant_id}?user_id={user_id}

    Add commands for project user quotas management.
     - Show user quotas:
       nova-manage project quota --project <Project name> --user <User name>
     - Update/Create user quotas:
       nova-manage project quota --project <Project name> --user <User name>
       --key <key> --value <value>

This new feature should have documentation added in the quotas section, cli guide updated, and api ref updated

[Diane Fleming (diane-fleming)]

backport: havana

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/64401

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/64594

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/64401
Committed: https://git.openstack.org/cgit/openstack/api-site/commit/?id=838718c80735f625633387d8ce1318261cae89ea
Submitter: Jenkins
Branch: master

commit 838718c80735f625633387d8ce1318261cae89ea
Author: Miranda Zhang <email address hidden>
Date: Mon Dec 30 08:03:41 2013 +0000

    Modify API ref for per-project-user quotas CRUD methods

    **tenant** is an entity that owns the resources,
    sometines called a project, sometimes the same as
    a user

    In addition to the owning entity (tenant), openstack
    stores the entity performing the action as the **user**.

    1st tenant ID in the URI, is the ID of the admin user
    2ed tenant ID in the URI, is the project ID/Name
    User ID is specified vis query string.
    (I tried my best to express what I mean using the
    current WADL markup.)

    Changed the url path structure.
    http://api.openstack.org/api-ref-compute.html#os-quota-sets

    Changed the sample responses to point to the new ones in
    /api_samples/os-user-quotas/

    For the other part, in the original bug description:
    Add commands for project user quotas management.
         - Show user quotas:
           nova-manage project quota --project <Project name>
           --user <User name>
         - Update/Create user quotas:
           nova-manage project quota --project <Project name>
           --user <User name> --key <key> --value <value>
    I found this page:
    https://wiki.openstack.org/wiki/NovaManage
    "The nova-manage isn't properly documented, but it's going away
    in Folsom, so using this wiki page for quick docs on it."

    Looks like the usage of this method still needs further
    validation, so dose the API call.
    It may need to be futher documented in
    docs.openstack.org/trunk/openstack-ops/content/quotas.html

    In the response:
    "fixed_ips": -1
    Does not seem to be right to have negative value for number
    of IPs.
    docs.openstack.org/user-guide-admin/content/cli_set_quotas.html
    "Number of fixed IP addresses allowed per tenant. This number
    must be equal to or greater than the number of allowed
    instances."

    Change-Id: Id4e08170ebf04ebb4ba846bf8b576a228b91441b
    Closes-Bug: #1187277