cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinandan Prateek (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-8592) Enhance usage server to provide quota service
Date Wed, 04 Nov 2015 03:10:27 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abhinandan Prateek updated CLOUDSTACK-8592:
-------------------------------------------
    Fix Version/s:     (was: 4.6.0)
                   4.7.0

> Enhance usage server to provide quota service
> ---------------------------------------------
>
>                 Key: CLOUDSTACK-8592
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8592
>             Project: CloudStack
>          Issue Type: Task
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Usage
>    Affects Versions: 4.6.0
>            Reporter: Abhinandan Prateek
>            Assignee: Abhinandan Prateek
>            Priority: Critical
>             Fix For: 4.7.0
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Quota+Service+-+FS
> Quota service while allowing for scalability will make sure that the cloud is not exploited
by attacks, careless use and program errors. To address this problem, we propose to employ
a quota-enforcement service that allows resource usage within certain bounds as defined by
policies and available quotas for various entities. 
> Quota service extends the functionality of usage server to provide a measurement for
the resources used by the accounts and domains using a common unit referred to as cloud currency
in this document. It can be configured to ensure that your usage won’t exceed the budget
allocated to accounts/domain in cloud currency.
> It will let user know how much of the cloud resources he is using. It will help the cloud
admins, if they want, to ensure that a user does not go beyond his allocated quota. Per usage
cycle if a account is found to be exceeding its quota then it is locked. Locking an account
means that it will not be able to initiat
> e a new resource allocation request, whether it is more storage or an additional ip.
Needless to say quota service as well as any action on the account is configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message