Bug 1370560 - [RFE] Restriction on individual disk and vm allocation
Summary: [RFE] Restriction on individual disk and vm allocation
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 4.0.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Rob Young
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-26 15:19 UTC by Allie DeVolder
Modified: 2020-08-03 15:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-13 14:26:04 UTC
oVirt Team: Virt
Target Upstream Version:
lsvaty: testing_plan_complete-

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Allie DeVolder 2016-08-26 15:19:14 UTC 
Current quota systems allow for maximum amounts of resources allowed per user, but we need the ability to set maximum size of individual components, such as a maximum disk size and a maximum amount of RAM per VM.

Examples:
- A normal user should not able to create new vm more then 4 GB ram
- user should not able to create/attach disk more them 30GB size
Comment 2 Allon Mureinik 2016-08-28 07:58:27 UTC 
Doron/Roy - this sounds more of an SLA issue than a virt issue, doesn't it?
Comment 3 Doron Fediuck 2016-08-31 09:03:00 UTC 
(In reply to Allon Mureinik from comment #2)
> Doron/Roy - this sounds more of an SLA issue than a virt issue, doesn't it?

It could be if we consider extending the existing quota or using a similar mechanism.
Comment 6 Marina Kalinin 2019-08-30 18:33:23 UTC 
Ryan, wouldn't this RFE be resolved by this one bz 1193815 ?
Comment 7 Ryan Barry 2019-08-30 18:36:55 UTC 
Not necessarily -- it depends on how extensive any changes there would be
Comment 8 Michal Skrivanek 2020-03-10 12:25:40 UTC 
change SLA team to virt, we're not tracking SLA separately anymore
Note You need to log in before you can comment on or make changes to this bug.