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:
*** Bug 859767 has been marked as a duplicate of this bug. ***
*** Bug 950076 has been marked as a duplicate of this bug. ***
*** Bug 1132256 has been marked as a duplicate of this bug. ***
ovirt-3.6.0-3 release
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
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 -.
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
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
(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!
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