[Engine-devel] 'Import VM/Template More Than Once' feature

Gilad Chaplik gchaplik at redhat.com
Thu Mar 29 19:49:00 UTC 2012


I think that the necessity of this feature is a from UX point of view:
Avoiding the nasty can-do-action if the VM is in the system, and adding an important flow to the user.

Anyhow I think it's a light feature with minimum changes to the backend, most of the work is in the ui.

Thanks, 
Gilad.

----- Original Message -----
> From: "Livnat Peer" <lpeer at redhat.com>
> To: "Gilad Chaplik" <gchaplik at redhat.com>
> Cc: engine-devel at ovirt.org
> Sent: Thursday, March 29, 2012 10:56:17 AM
> Subject: Re: [Engine-devel] 'Import VM/Template More Than Once' feature
> 
> On 21/02/12 17:11, Gilad Chaplik wrote:
> > Hello all,
> > 
> > The 'Import VM/Template More Than Once' feature description can be
> > found under the following link:
> > 
> > http://www.ovirt.org/wiki/Features/ImportMoreThanOnce
> > 
> > Please review, and feel free to share your comments and thoughts.
> > 
> > Thanks,
> > Gilad.
> 
> I am missing the most obvious limitation of this feature in the
> summary
> of the feature.
> 
> This feature is limited to mode of collapsing the imported VM images
> AFAIR, if you import a VM based on a template, for each import, a
> collapsed image is created in the setup (It is like importing the
> template with each VM you have based on this template).
> 
> I think this limitation makes the feature unworthy, we should be able
> to
> support changing the ID's and importing only the needed storage
> layer.
> 
> 
> Livnat
> 
> > 
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/engine-devel
> 
> 



More information about the Engine-devel mailing list