
----- Original Message -----
From: "Andrew Cathrow" <acathrow@redhat.com> To: "Itamar Heim" <iheim@redhat.com>, "Dan Yasny" <dyasny@redhat.com>, "Ricky Hopper" <Ricky.Hopper@netapp.com> Cc: engine-devel@ovirt.org Sent: Wednesday, August 1, 2012 12:24:42 AM Subject: Re: [Engine-devel] Domain rescan action question
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Ricky Hopper" <Ricky.Hopper@netapp.com> Cc: engine-devel@ovirt.org Sent: Tuesday, July 31, 2012 4:44:34 PM Subject: Re: [Engine-devel] Domain rescan action question
On 07/31/2012 11:30 PM, Hopper, Ricky wrote:
Hey all,
As I'm making progress with the domain rescan functionality, I've realized that I'm unsure what to do with any disks that are detected on the domain. Should I add them back into the database to be listed as floating disks, or should I just return a list of disk images to be attached to whatever the caller of the query needs?
- Ricky
i'm not sure they should be added automatically. I think a dialog[1] showing orphan disks/images on the storage domain for user to choose which to import as 'floating' disks would be better than auto importing them.
there is also the reverse of flagging existing disks as 'missing' in storage?
Perhaps we should start a feature page to discuss and better scope it. There is a feature page that we could expand, it doesn't discuss the notion of importing those disks which is certainly something we need to address.
+1 also, how will be handled images with snapshots? or broken chain of images (not sure its a valid scenario)
[1] or a subtab on the storage domain.
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel