Difference between revisions of "DomainQuotaManagementAndEnforcement"
m |
m |
||
Line 70: | Line 70: | ||
== Design == | == Design == | ||
The proposal is to extend Keystone and existing service quota drivers to support the domain quotas management and enforcement. The following figure depicts the high level architecture. | The proposal is to extend Keystone and existing service quota drivers to support the domain quotas management and enforcement. The following figure depicts the high level architecture. | ||
− | + | [[File:Domainquota.png|frameless]] | |
Our idea is to concentrate the REST APIs in the Domain Quota Proxy which will be in charge of: | Our idea is to concentrate the REST APIs in the Domain Quota Proxy which will be in charge of: | ||
• Distributing domain quotas to the services | • Distributing domain quotas to the services |
Revision as of 20:17, 7 June 2013
- Launchpad Entry: Domain Quota Management
- Created: 03 March 2013
- Contributors: Yehia Beyh, Glaucimar Aguiar , Tiago Martins, Rodrigo Antunes
Contents
Introduction
In Keystone v3 (Grizzly release), Domains encapsulates users and projects into logical entities that can represent accounts, organizations, etc. Currently there is no capability or mechanism to manage or enforce quotas at domain level. Assigning or updating quota values or limits to a domain will allow the cloud administrator to evaluate domain lists and consumption. In order to achieve these capabilities it will be required to implement quota management for Keystone domains. The goal of this blueprint is to support quotas at the OpenStack Domain level. The design of the feature models, as far as possible, the style of project quotas.
Openstack Quotas
Today OpenStack services make usage of quotas to limit the project resources. For example, the “Instances” quota represents the number of instances that can be created in a project. The table below summarizes the existing project quotas.
quotas | type | default values | description |
---|---|---|---|
nova.instances | reservable | 10 | number of instances allowed per project |
nova.cores | reservable | 20 | number of instance cores allowed per project |
nova.ram | reservable | 50*1024 | megabytes of instance ram allowed per project |
nova.floating_ips | reservable | 10 | number of floating ips allowed per project |
nova.fixed_ips | reservable | -1 | number of fixed ips allowed per project |
nova.metadata_items | absolute | 128 | number of metadata items allowed per instance |
nova.injected_files | absolute | 5 | number of injected files allowed |
nova.injected_files_content_bytes | absolute | 10*1024 | number of bytes allowed per injected file |
nova.injected_file_path_bytes | absolute | 255 | number of bytes allowed per injected file path |
nova.security_groups | reservable | 10 | number of security groups per project |
nova.security_groups_rules | countable | 20 | number of security rules per security group |
nova.key_pairs | countable | 100 | number of key pairs per user |
cinder.volumes | reservable | 10 | number of volumes allowed per project |
cinder.snapshots | reservable | 10 | number of volume snapshots allowed per project |
cinder.gigabytes | reservable | 1000 | number of volume gigabytes (snapshots are also included) per project |
quantum.network | countable | 10 | Number of networks allowed per tenant |
quantum.subnet | countable | 10 | Number of subnets allowed per tenant |
quantum.port | countable | 50 | number of ports allowed per tenant |
User Stories
Domain Quotas might impact partitioned OpenStack deployments (regions, cells, etc). Here we consider only the impact on regions. These can be
- Per–Region domain quotas
- Across region domain quotas
The 1st approach works similar to the current implementation of quotas per project; in a multi-region scenario, the domain quotas are enforced by each service in a non-centralized fashion. The 2nd approach, a domain quota is shared dynamically among regions, e.g. if a service from a given region needs more quota than the others, it requests more quotas. This blueprint addresses the per–region domain quotas. The user stories are listed below:
- As a cloud administrator, I want to create a domain with default domain quotas
- As a cloud/domain administrator, I want to see the domain quotas for a domain in a region
- As a cloud/domain administrator, I want to see the domain quotas usage for a domain in a region
- As a cloud administrator, I want to update the quotas for a domain in a region
- As a cloud administrator, I want to delete the quotas for a domain in a region
Since quotas deals with sensible aspects of resource consumption, we identified the need to log the interactions of users when they manage domain quotas.
Design
The proposal is to extend Keystone and existing service quota drivers to support the domain quotas management and enforcement. The following figure depicts the high level architecture. Our idea is to concentrate the REST APIs in the Domain Quota Proxy which will be in charge of: • Distributing domain quotas to the services • Gathering domain quotas usage from the services Quota modules need to be refactored to add a driver to enforce domain quotas. Also we should extend the services REST API to provide domain quotas usage to Domain Quota Proxy. The Domain Quota Proxy is designed to be implemented as a discrete extension and not included in the default pipeline of Keystone. The Domain Quota Driver design is similar to the current quota driver from quota.py module, given the possibility to the user to option to use it or not; they will be responsible to enforce all quotas listed in the table above in the context of domains.
REST API
This gives an option of getting quota for all domains. Region is optional, if not informed, it returns for all regions.
GET v3/os-domain-quotas Content-Type application/json Accept application/json
Request:
{ "quota_set":{ "region": "regionOne" "nova": [ "instances", "volumes", "floating_ips" ] "cinder": [ "volumes","gigabytes" ] } }
Normal Response Code: 200
Error Response Codes: Unauthorized (401), Not Found (404)
Response:
This gives an option of getting quota for single domain only.
GET v3/{domain-id}/os-domain-quotas Content-Type application/json Accept application/json
Request:
{ "quota_set":{ "region": "regionOne", "services":[ "nova", "cinder" ] } }
Normal Response Code: 200
Error Response Codes: Unauthorized (401), Not Found (404)
Response:
{ "quota_set":{ "region":"RegionOne", "nova":{ "instances": 10 "cores": 20 "ram": 1024 "fixed_ips": -1 "volumes": 20, "floating_ips": 10 "metada_items": 128 "injected_files": 5 "injected_files_content_bytes":1024 "injected_file_path_bytes": 255 "security_groups": 10 "security_groups_rules": 20 "key_pairs": 100 } "cinder":{ "volumes": 20 "snapshots":10 "gigabytes": 2048 } } }
This gives an option of setting quota for single domain only.
SET v3/{domain-id}/os-domain-quotas Content-Type application/json Accept application/json
Request:
{ "quota_set":{ "region":"RegionOne", "nova":{ "volumes": 20, "floating_ips": 10 } } }
Normal Response Code: 200
Error Response Codes: Unauthorized (401), Not Found (404)
Response:
{ "quota_set":{ "region":"RegionOne", "nova":{ "instances": 10 "cores": 20 "ram": 1024 "fixed_ips": -1 "volumes": 20, "floating_ips": 10 "metada_items": 128 "injected_files": 5 "injected_files_content_bytes":1024 "injected_file_path_bytes": 255 "security_groups": 10 "security_groups_rules": 20 "key_pairs": 100 } } }
This gives an option of updating quota for single domain only.
POST v3/{domain-id}os-domain-quotas Content-Type application/json Accept application/json
Request
{ "quota_set":{ "region":"RegionOne", "nova":{ "volumes": 25, "floating_ips": 30 } } }
Normal Response Code: 200
Error Response Codes: Unauthorized (401), Not Found (404)
Response:
{ "quota_set":{ "region":"RegionOne", "nova":{ "instances": 10 "cores": 20 "ram": 1024 "fixed_ips": -1 "volumes": 25, "floating_ips": 30 "metada_items": 128 "injected_files": 5 "injected_files_content_bytes":1024 "injected_file_path_bytes": 255 "security_groups": 10 "security_groups_rules": 20 "key_pairs": 100 } } }
This gives an option of deleting quota for single domain only.
DELETE v3/{domain-id}/os-domain-quotas Content-Type application/json Accept application/json
Request:
{ "quota_set": { "region": "regionOne", "nova": [ "instances", "volumes", "floating_ips" ], "cinder": [ "volumes", "gigabytes" ] } }
Normal Response Code: 200
Error Response Codes: Unauthorized (401), Not Found (404)
Response:
{ "quota_set":{ "region":"RegionOne", "nova":{ "instances": 10 "cores": 20 "ram": 1024 "fixed_ips": -1 "volumes": 20, "floating_ips": 10 "metada_items": 128 "injected_files": 5 "injected_files_content_bytes":1024 "injected_file_path_bytes": 255 "security_groups": 10 "security_groups_rules": 20 "key_pairs": 100 } "cinder":{ "volumes": 20 "snapshots":10 "gigabytes": 2048 } } }
Open Stack Quota References
This is a list of URLs of work on quotas within OpenStack.