Re: [Engine-devel] Domain rescan action question
On 08/02/2012 04:44 AM, Shu Ming wrote: No comments below. I am just curious how you can have disk created outside of the oVirt environment if the storage domain is mounted on oVirt engine. Does your application try to communicate with VDSM though SPM host to do that? Are the two applications(oVirt engine and your application) coexisting and manipulating the storage domain at the same time or one application is quiet when the other one is functioning? IMHO, modifying the storage domain meta data from two application are dangerous and I suppose your application should know the reason and what these disks are for. So telling oVirt to import the disks automatically should be reasonable because you know what these disks are for and it is unnecessary for the oVirt administrator to select which one to import. two use cases: 1. NFS storage allows this quite easily, and very relevant with storage side cloning. 2. engine and storage go out of sync (recover either from backup) On 2012-8-2 1:36, Hopper, Ricky wrote: On 8/1/12 10:05 AM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Ricky Hopper ricky.hop...@netapp.com To: Dan Yasny dya...@redhat.com Cc: engine-devel@ovirt.org, Itamar Heim ih...@redhat.com, Andrew Cathrow acath...@redhat.com Sent: Wednesday, 1 August, 2012 4:56:45 PM Subject: Re: [Engine-devel] Domain rescan action question On 8/1/12 9:42 AM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Ricky Hopper ricky.hop...@netapp.com To: Dan Yasny dya...@redhat.com, Andrew Cathrow acath...@redhat.com Cc: engine-devel@ovirt.org, Itamar Heim ih...@redhat.com, Ricky Hopper ricky.hop...@netapp.com Sent: Wednesday, 1 August, 2012 4:34:53 PM Subject: Re: [Engine-devel] Domain rescan action question On 8/1/12 5:59 AM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Andrew Cathrow acath...@redhat.com To: Itamar Heim ih...@redhat.com, Dan Yasny dya...@redhat.com, Ricky Hopper ricky.hop...@netapp.com Cc: engine-devel@ovirt.org Sent: Wednesday, 1 August, 2012 12:24:42 AM Subject: Re: [Engine-devel] Domain rescan action question - Original Message - From: Itamar Heim ih...@redhat.com To: Ricky Hopper ricky.hop...@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. http://wiki.ovirt.org/wiki/Features/Orphaned_Images The original idea was to scan the storage domains and compare the images lists to the database, thus getting a list of images no longer relevant and scrubbing the storage. This will actually be addressed properly in the future (Ayal can elaborate on that) but for now this is needed at least for that use case. As I understand, the conversation here is about trying to take an already populated SD (from another setup I suppose), scanning it and putting it into RHEV? As I understood it, the purpose of this functionality wasn't to find images which should be removed from storage, but to find images on the domain that oVirt was unaware of and importing them for use (for instance, if a disk was created outside of oVirt on the domain). If one of the use cases for this feature is also the orphaned images mentioned on the feature page, that may expand the functionality into a separate domain scrub and storage import, both of which would call the rescan (meaning the rescan would not actually add to the database, but instead return a list of orphaned disk images). Another solution would be to import all disk images into the database either way, and let the user delete any orphaned images from the GUI. I think are nice to have, but the problem with the scanning is that if we're not scanning a master domain or an export domain, all we will see is a bunch of images with no context or even hints as to where they belong. The data that makes it all usable is in the engine database and in the ovf files on the master domain. This is why I stopped at the orphaned images part of the feature - because there it's feasible, I would
[Engine-devel] Fwd: [jboss-rpm] New jboss-as update (7.1.1-6)
fyi Original Message Subject: [jboss-rpm] New jboss-as update (7.1.1-6) Date: Thu, 02 Aug 2012 10:47:28 +0200 From: Marek Goldmann mgold...@redhat.com To: jboss-...@lists.jboss.org jboss-...@lists.jboss.org Hi all, I just submitted a new update (7.1.1-6) to Fedora. This is a bugfix release which fixes issues with oVirt: - https://bugzilla.redhat.com/show_bug.cgi?id=843285 - https://bugzilla.redhat.com/show_bug.cgi?id=844554 - https://bugzilla.redhat.com/show_bug.cgi?id=842997 - https://bugzilla.redhat.com/show_bug.cgi?id=842996 (All above issues are talking about the same thing) Additionally a fix preventing the package from building from source was applied. Once it hits testing, please give it a try and bump the karma: https://admin.fedoraproject.org/updates/jboss-as-7.1.1-6.fc17 Thanks! --Marek ___ jboss-rpm mailing list jboss-...@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-rpm ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Domain rescan action question
In the interest of good discussion, we've put up a feature page for this feature (http://wiki.ovirt.org/wiki/Features/Domain_Scan), which links to a talk page where modifications can be proposed to how I've laid out the feature. So far, it covers how the query works and which commands will come about to implement it. I'd appreciate it if anyone concerned could check this out and make any changes as they see fit so we can get going with the coding. - Ricky On 8/1/12 2:35 PM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Ricky Hopper ricky.hop...@netapp.com To: Dan Yasny dya...@redhat.com Cc: engine-devel@ovirt.org, Itamar Heim ih...@redhat.com, Andrew Cathrow acath...@redhat.com Sent: Wednesday, 1 August, 2012 8:36:09 PM Subject: Re: [Engine-devel] Domain rescan action question On 8/1/12 10:05 AM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Ricky Hopper ricky.hop...@netapp.com To: Dan Yasny dya...@redhat.com Cc: engine-devel@ovirt.org, Itamar Heim ih...@redhat.com, Andrew Cathrow acath...@redhat.com Sent: Wednesday, 1 August, 2012 4:56:45 PM Subject: Re: [Engine-devel] Domain rescan action question On 8/1/12 9:42 AM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Ricky Hopper ricky.hop...@netapp.com To: Dan Yasny dya...@redhat.com, Andrew Cathrow acath...@redhat.com Cc: engine-devel@ovirt.org, Itamar Heim ih...@redhat.com, Ricky Hopper ricky.hop...@netapp.com Sent: Wednesday, 1 August, 2012 4:34:53 PM Subject: Re: [Engine-devel] Domain rescan action question On 8/1/12 5:59 AM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Andrew Cathrow acath...@redhat.com To: Itamar Heim ih...@redhat.com, Dan Yasny dya...@redhat.com, Ricky Hopper ricky.hop...@netapp.com Cc: engine-devel@ovirt.org Sent: Wednesday, 1 August, 2012 12:24:42 AM Subject: Re: [Engine-devel] Domain rescan action question - Original Message - From: Itamar Heim ih...@redhat.com To: Ricky Hopper ricky.hop...@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. http://wiki.ovirt.org/wiki/Features/Orphaned_Images The original idea was to scan the storage domains and compare the images lists to the database, thus getting a list of images no longer relevant and scrubbing the storage. This will actually be addressed properly in the future (Ayal can elaborate on that) but for now this is needed at least for that use case. As I understand, the conversation here is about trying to take an already populated SD (from another setup I suppose), scanning it and putting it into RHEV? As I understood it, the purpose of this functionality wasn't to find images which should be removed from storage, but to find images on the domain that oVirt was unaware of and importing them for use (for instance, if a disk was created outside of oVirt on the domain). If one of the use cases for this feature is also the orphaned images mentioned on the feature page, that may expand the functionality into a separate domain scrub and storage import, both of which would call the rescan (meaning the rescan would not actually add to the database, but instead return a list of orphaned disk images). Another solution would be to import all disk images into the database either way, and let the user delete any orphaned images from the GUI. I think are nice to have, but the problem with the scanning is that if
Re: [Engine-devel] Domain rescan action question
Thanks Ricky, I've added reviewing this to my todo list Dan - Original Message - From: Ricky Hopper ricky.hop...@netapp.com To: Dan Yasny dya...@redhat.com Cc: engine-devel@ovirt.org Sent: Thursday, 2 August, 2012 5:37:10 PM Subject: Re: [Engine-devel] Domain rescan action question In the interest of good discussion, we've put up a feature page for this feature (http://wiki.ovirt.org/wiki/Features/Domain_Scan), which links to a talk page where modifications can be proposed to how I've laid out the feature. So far, it covers how the query works and which commands will come about to implement it. I'd appreciate it if anyone concerned could check this out and make any changes as they see fit so we can get going with the coding. - Ricky On 8/1/12 2:35 PM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Ricky Hopper ricky.hop...@netapp.com To: Dan Yasny dya...@redhat.com Cc: engine-devel@ovirt.org, Itamar Heim ih...@redhat.com, Andrew Cathrow acath...@redhat.com Sent: Wednesday, 1 August, 2012 8:36:09 PM Subject: Re: [Engine-devel] Domain rescan action question On 8/1/12 10:05 AM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Ricky Hopper ricky.hop...@netapp.com To: Dan Yasny dya...@redhat.com Cc: engine-devel@ovirt.org, Itamar Heim ih...@redhat.com, Andrew Cathrow acath...@redhat.com Sent: Wednesday, 1 August, 2012 4:56:45 PM Subject: Re: [Engine-devel] Domain rescan action question On 8/1/12 9:42 AM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Ricky Hopper ricky.hop...@netapp.com To: Dan Yasny dya...@redhat.com, Andrew Cathrow acath...@redhat.com Cc: engine-devel@ovirt.org, Itamar Heim ih...@redhat.com, Ricky Hopper ricky.hop...@netapp.com Sent: Wednesday, 1 August, 2012 4:34:53 PM Subject: Re: [Engine-devel] Domain rescan action question On 8/1/12 5:59 AM, Dan Yasny dya...@redhat.com wrote: - Original Message - From: Andrew Cathrow acath...@redhat.com To: Itamar Heim ih...@redhat.com, Dan Yasny dya...@redhat.com, Ricky Hopper ricky.hop...@netapp.com Cc: engine-devel@ovirt.org Sent: Wednesday, 1 August, 2012 12:24:42 AM Subject: Re: [Engine-devel] Domain rescan action question - Original Message - From: Itamar Heim ih...@redhat.com To: Ricky Hopper ricky.hop...@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. http://wiki.ovirt.org/wiki/Features/Orphaned_Images The original idea was to scan the storage domains and compare the images lists to the database, thus getting a list of images no longer relevant and scrubbing the storage. This will actually be addressed properly in the future (Ayal can elaborate on that) but for now this is needed at least for that use case. As I understand, the conversation here is about trying to take an already populated SD (from another setup I suppose), scanning it and putting it into RHEV? As I understood it, the purpose of this functionality wasn't to find images which should be removed from storage, but to find images on the domain that oVirt was unaware of and importing them for use (for instance, if a disk was created outside of oVirt on the domain). If one of the use cases for this feature is also the orphaned
