Bug 1062441
Summary: | [RFE] Provide ability to overcome ~300 instance effective limit on VM pools when using iSCSI or FC storage domain | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Simon Sekidde <ssekidde> | |
Component: | ovirt-engine | Assignee: | Michal Skrivanek <michal.skrivanek> | |
Status: | CLOSED DUPLICATE | QA Contact: | ||
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 3.3.0 | CC: | abaron, amureini, gklein, iheim, lpeer, mjs, rbalakri, Rhev-m-bugs, scohen, sherold, ssekidde, yeylon | |
Target Milestone: | --- | Keywords: | FutureFeature | |
Target Release: | --- | Flags: | scohen:
needinfo+
amureini: needinfo- sherold: Triaged+ |
|
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | virt | |||
Fixed In Version: | Doc Type: | Enhancement | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1066135 (view as bug list) | Environment: | ||
Last Closed: | 2015-03-31 09:57:01 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1066135 |
Description
Simon Sekidde
2014-02-06 23:56:34 UTC
You can create multiple storage domains in the same pool. The limitation is 350 per storage domain, not per pool. I'm not sure what is being requested here? (unless we're discussing lifting the lvm limitations in which case this bug should be against lvm). Simon - this RFE seems to be about enhancing the storage domain using LVM to perform better so it won't be limited to 300 disks per storage domain (which i think is worth keeping). if relevant, can you please open a separate RFE to "support pools across multiple storage domains", so a pool could be created with more than 300 VMs, just using multiple storage domains? Customer is looking for functional solution, does not care too much about method of implementation. Goal: Use FC storage, be able to create a desktop VM pool with 1000+ plus guest instances. If the recommended functional solution is to support VM pools across multiple SD, then that should be sufficient. The misunderstanding was around the word 'pool'. The requirement here is to be able to provision a VM pool on multiple storage domains. A VM pool is created from a template. the template can have copies of its disks on multiple domains (this is supported right now). What we need to verify is that when creating a VM pool the user can choose which domains to use for provisioning the disks of the VMs. In this way the user could create multiple pools from the same template but on different storage domains and effectively bypass the limitations. A possible enhancement (definitely not supported atm) would be to provision a single vm pool with pool VMs created on multiple domains (allow user to choose per disk how many would be created on each domain). Correct - and one more functional point, just to clarify the word "user": * It is acceptable for the RHEV Administrator to see the "rough edges" of having multiple storage domains, * The consumer of the VDI service should only see a single VM pool in the User Portal, and the selection of which storage domain will contain this user's instance must be kept completely invisible from this consuming user. |