GBP forces me to adjust quotas in neutron

[AJAY KALAMBUR]

Currently when using GBP since its Application intent driven would be good to have the quota adjustment per tenant also done using GBP. If not as an admin i need to first adjust the quotas in neutron for networks, ports, subnets etc which means again i speak networking language rather than intent

Provide a way to specify quotas in GBP Intent rather than in neutron

Else while performing scale tests i run out of quota and need to adjust that in neutron

[Sumit Naiksatam (snaiksat)]

I believe this would be in the domain of the RMD design.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/208200
Committed: https://git.openstack.org/cgit/stackforge/group-based-policy/commit/?id=a2850d8c58ac07931e3de6c8a6185b147ce02512
Submitter: Jenkins
Branch: master

commit a2850d8c58ac07931e3de6c8a6185b147ce02512
Author: Sumit Naiksatam <email address hidden>
Date: Sun Aug 2 05:38:05 2015 -0700

    Adds quota support for GBP resources

    GBP quota enforcement tracks both, explicitly
    created and implicitly created GBP resources.

    Enforcement is done in two places:

    1. At the API layer using the standard mechanism,

    2. At the DB layer for implicitly created resources.

    By default all GBP quota limits are set to -1, i.e.,
    the quota is unlimited.

    Change-Id: I44eda4cf0c70feebd3453e56bf6af45eef6340bd
    Closes-bug: 1462066

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/juno
Review: https://review.openstack.org/213403

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/213403
Committed: https://git.openstack.org/cgit/stackforge/group-based-policy/commit/?id=da46b217a3be184661104d750dc884ca42da5230
Submitter: Jenkins
Branch: stable/juno

commit da46b217a3be184661104d750dc884ca42da5230
Author: Sumit Naiksatam <email address hidden>
Date: Sun Aug 2 05:38:05 2015 -0700

    Adds quota support for GBP resources

    GBP quota enforcement tracks both, explicitly
    created and implicitly created GBP resources.

    Enforcement is done in two places:

    1. At the API layer using the standard mechanism,

    2. At the DB layer for implicitly created resources.

    By default all GBP quota limits are set to -1, i.e.,
    the quota is unlimited.

    Change-Id: I44eda4cf0c70feebd3453e56bf6af45eef6340bd
    Closes-bug: 1462066
    (cherry picked from commit a2850d8c58ac07931e3de6c8a6185b147ce02512)