Bug 893927

Summary: [RFE] Implement quota support in API
Product: Red Hat Enterprise Virtualization Manager Reporter: Ondra Machacek <omachace>
Component: ovirt-engineAssignee: Doron Fediuck <dfediuck>
Status: CLOSED ERRATA QA Contact: Artyom <alukiano>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: alukiano, bazulay, bsettle, dfediuck, gklein, iheim, istein, juwu, lsurette, lsvaty, mavital, oramraz, pnovotny, rbalakri, Rhev-m-bugs, sherold, s.kieske, yeylon, ykaul
Target Milestone: ovirt-3.6.0-rcKeywords: FutureFeature, Triaged
Target Release: 3.6.0Flags: sgrinber: Triaged+
Hardware: Unspecified   
OS: Unspecified   
URL: http://www.ovirt.org/Features/Quota
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
With this update, you can configure quotas using the REST API. New entities such as QuotaStorageLimit and QuotaClusterLimit were added to the quotas sub-collection. QuotaStorageLimit allows you to specify a quota policy for individual or all storage domains. QuotaClusterLimit allows you to specify the Memory and CPU limit for individual or all clusters in a data center.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-09 20:28:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 950076, 1132506    

Description Ondra Machacek 2013-01-10 09:32:41 UTC
Description of problem:
Please implement quota support in API.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 3 Michael Pasternak 2013-01-30 16:01:40 UTC
*** Bug 859767 has been marked as a duplicate of this bug. ***

Comment 7 Doron Fediuck 2014-05-08 16:16:07 UTC
*** Bug 950076 has been marked as a duplicate of this bug. ***

Comment 8 Doron Fediuck 2014-11-25 16:25:23 UTC
*** Bug 1132256 has been marked as a duplicate of this bug. ***

Comment 13 Max Kovgan 2015-06-28 14:12:49 UTC
ovirt-3.6.0-3 release

Comment 14 Artyom 2015-10-27 08:24:22 UTC
Verified on rhevm-3.6.0.2-0.1.el6.noarch
1) Add, update and remove of quota
2) Change datacenter quota mode
3) Add limits to quota(storage, cluster)
4) Add consumer to quota
5) Attach quota to vm
6) Attach quota to disk

Comment 16 Julie 2016-02-23 02:00:40 UTC
If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format:

Cause:
Consequence:
Fix:
Result:

The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Comment 17 Julie 2016-02-29 05:32:17 UTC
hi Doron and Artyom, I have updated the doc text; however, it seems there should also be entities to allow assigning quotas per object, for example vms and disks. Could you advise?

Cheers,
Julie

Comment 18 Artyom 2016-02-29 13:28:33 UTC
I believe such option exist from 3.4:
for for example to update vm with quota:
<vm>
  <quota id="408039c9-e6e9-41bc-8e85-4476f0f13c0d"/>
</vm>

to update disk with quota:
<disk>
  <quota id="408039c9-e6e9-41bc-8e85-4476f0f13c0d"/>
</disk>

With name it show, that update succeed but vm and disk stay with old quota.
https://bugzilla.redhat.com/show_bug.cgi?id=1312896

Comment 19 Julie 2016-02-29 23:51:07 UTC
(In reply to Artyom from comment #18)
> I believe such option exist from 3.4:
> for for example to update vm with quota:
> <vm>
>   <quota id="408039c9-e6e9-41bc-8e85-4476f0f13c0d"/>
> </vm>
> 
> to update disk with quota:
> <disk>
>   <quota id="408039c9-e6e9-41bc-8e85-4476f0f13c0d"/>
> </disk>
> 
> With name it show, that update succeed but vm and disk stay with old quota.
> https://bugzilla.redhat.com/show_bug.cgi?id=1312896

Thanks!

Comment 21 errata-xmlrpc 2016-03-09 20:28:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0376.html