| Summary: | [RFE] - Add the ability to import multiple VM's from same VM residing on export domain | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Avihai <aefrat> |
| Component: | RFEs | Assignee: | Rob Young <royoung> |
| Status: | CLOSED DEFERRED | QA Contact: | meital avital <mavital> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | aefrat, bugs, michal.skrivanek, tjelinek |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | Flags: | michal.skrivanek:
ovirt-future?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Avihai
2016-11-24 09:36:32 UTC
can you please give some example use why would you want to import many times the same VM? Yes , If for example I want to take a VM already existing at the export domain and import/duplicated it many times to create a pool of VM's with similar characteristics . Currently this can only be done only importing one by one VM from an existing VM at export domain which is much less effective IMHO . So import that one VM once and create a pool based on it? Yes , in your way you need 2 steps ( this can be implemented as you suggested) : 1) import VM 2) create a pool based on that VM What I want to to directly in 1 step : choose a VM already existing at the export domain and import/duplicated it many times to create a pool of VM's with similar characteristics . We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it. If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly. ok, closing. Please reopen if still relevant/you want to work on it. ok, closing. Please reopen if still relevant/you want to work on it. |