Extend neutron quota to support vips, pools, members and health monitors
Currently, neutron LBaaS entities have no quota support.
Need to extend neutron quota to support vips, pools, members and health monitors
Blueprint information
- Status:
- Complete
- Approver:
- Mark McClain
- Priority:
- Medium
- Drafter:
- Evgeny Fedoruk
- Direction:
- Approved
- Assignee:
- Evgeny Fedoruk
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Evgeny Fedoruk
- Completed by
- Mark McClain
Whiteboard
The purpose of this blueprint is to describe the extension of quota mechanism for neutron LBaaS entities.
Currently, neutron LBaaS entities have no quota support.
Need to add quota for vips, pools, members and health monitors.
Default values:
vips limit default = 10
pools limit default = 10
members limit default = -1
health monitors limit default = -1
Note:Members and health monitors have unlimited value as a default because they are not real
resource consumers on OpenStack. Quota is still an option because on back-end they
are resource consumers and hence may be limited.
DB migration:
Since quotas table has structure that allows adding new resources
without changing table structure (<resource, value> structure),
no migration script is needed.
Upgrade use case:
Tenant has amount of resource which is grater than new quota.
Adding another entity will be forbidden by the extended quota opts
by checking the default values. Since DB will not have new resources' quotas
before project quotas will be edited and saved in Horizon or via CLI.
There will be no problem to delete "extra" entities.
Following projects should be changed:
neutron project - add new entities to the quota ops and driver
python-
horizon - add new entities to the openstack-dashboard
tempest - add new resource to tempest neutron quota testing
Gerrit topic: https:/
Addressed by: https:/
Addressed by: https:/
Addressed by: https:/
Addressed by: https:/
