Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On 11/28/2013 03:53 AM, Haim Ateya wrote: - Original Message - From: Bob Doolittle b...@doolittle.us.com To: d...@redhat.com Cc: users@ovirt.org Sent: Wednesday, November 27, 2013 12:16:30 AM Subject: Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain On 11/26/2013 03:27 PM, Dafna Ron wrote: sql -U postgres engine -c 'select connection from storage_server_connections;' So now that we determined that I have stale connection state in my DB, any suggestions as to how I might clear it out safely? I tried rebooting my Engine, but the connection is still in the DB and it still doesn't show in the Admin Portal. Hi Bob, you can try the following command: engine=# delete FROM storage_server_connections where connection = '172.16.0.58:/export/VM_EXPORTDOMAIN'; this should allow you re-create your storage domain. Thanks Haim! I would appreciate if you could file a bug against it. I got into this situation with some unsupported hacking, and am not sure whether I would have hit this same issue without it or not. Do you believe this stale data was simply a result of trying to add a Host while it had a default iptables configuration active? If it's that simple I'm happy to open the bug. But if it was a result of trying to manually convert an old Data NFS Domain into an Export NFS Domain that's not worth opening a bug since an official feature to do this is in development. Please advise. Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
- Original Message - From: Bob Doolittle b...@doolittle.us.com To: d...@redhat.com Cc: users@ovirt.org Sent: Wednesday, November 27, 2013 12:16:30 AM Subject: Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain On 11/26/2013 03:27 PM, Dafna Ron wrote: sql -U postgres engine -c 'select connection from storage_server_connections;' So now that we determined that I have stale connection state in my DB, any suggestions as to how I might clear it out safely? I tried rebooting my Engine, but the connection is still in the DB and it still doesn't show in the Admin Portal. Hi Bob, you can try the following command: engine=# delete FROM storage_server_connections where connection = '172.16.0.58:/export/VM_EXPORTDOMAIN'; this should allow you re-create your storage domain. I would appreciate if you could file a bug against it. Thanks, Bob On 11/26/2013 08:21 PM, Bob Doolittle wrote: On 11/26/2013 03:11 PM, Dafna Ron wrote: can you check the engine data base for the connection? Sorry, will need more guidance for that :( -Bob On 11/26/2013 07:12 PM, Bob Doolittle wrote: On 11/26/2013 02:00 PM, Dafna Ron wrote: can you run mount and see if you have stale connections to the domain? The only existing mounts on the Host are the loopback mount for the Data Domain, and the mount from Engine for the ISO Domain. I can import another Export domain on the same host which was created in the normal manner (and then 'destroy' it), but I can't import the converted one. -Bob On 11/26/2013 06:22 PM, Bob Doolittle wrote: Hi, I am having to recreate my engine, and want to recover my old VMs from the previous Storage Master Data Domain. A while back, Michael Ayers posted this recipe (the gmane reply feature won't allow lines longer than 80 chars, even if they were from the original post :(, so I apologize for the link ) : http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428 Should this method still work? I have tried to recreate this with 3.3.1 and can't. I copied over the old Data Domain to a new directory, and edited the dom_md/metadata file as follows: http://pastebin.com/U4xJawR8 But when I try to import it, I get: Error while executing action: Cannot add Storage Connection. Storage connection already exists. and Failed to retrieve existing storage domain information. Here's output from engine.log: http://pastebin.com/NVdzLDXb Any clues? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
Hi, I am having to recreate my engine, and want to recover my old VMs from the previous Storage Master Data Domain. A while back, Michael Ayers posted this recipe (the gmane reply feature won't allow lines longer than 80 chars, even if they were from the original post :(, so I apologize for the link ) : http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428 Should this method still work? I have tried to recreate this with 3.3.1 and can't. I copied over the old Data Domain to a new directory, and edited the dom_md/metadata file as follows: http://pastebin.com/U4xJawR8 But when I try to import it, I get: Error while executing action: Cannot add Storage Connection. Storage connection already exists. and Failed to retrieve existing storage domain information. Here's output from engine.log: http://pastebin.com/NVdzLDXb Any clues? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
can you run mount and see if you have stale connections to the domain? On 11/26/2013 06:22 PM, Bob Doolittle wrote: Hi, I am having to recreate my engine, and want to recover my old VMs from the previous Storage Master Data Domain. A while back, Michael Ayers posted this recipe (the gmane reply feature won't allow lines longer than 80 chars, even if they were from the original post :(, so I apologize for the link ) : http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428 Should this method still work? I have tried to recreate this with 3.3.1 and can't. I copied over the old Data Domain to a new directory, and edited the dom_md/metadata file as follows: http://pastebin.com/U4xJawR8 But when I try to import it, I get: Error while executing action: Cannot add Storage Connection. Storage connection already exists. and Failed to retrieve existing storage domain information. Here's output from engine.log: http://pastebin.com/NVdzLDXb Any clues? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On 11/26/2013 02:00 PM, Dafna Ron wrote: can you run mount and see if you have stale connections to the domain? The only existing mounts on the Host are the loopback mount for the Data Domain, and the mount from Engine for the ISO Domain. I can import another Export domain on the same host which was created in the normal manner (and then 'destroy' it), but I can't import the converted one. -Bob On 11/26/2013 06:22 PM, Bob Doolittle wrote: Hi, I am having to recreate my engine, and want to recover my old VMs from the previous Storage Master Data Domain. A while back, Michael Ayers posted this recipe (the gmane reply feature won't allow lines longer than 80 chars, even if they were from the original post :(, so I apologize for the link ) : http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428 Should this method still work? I have tried to recreate this with 3.3.1 and can't. I copied over the old Data Domain to a new directory, and edited the dom_md/metadata file as follows: http://pastebin.com/U4xJawR8 But when I try to import it, I get: Error while executing action: Cannot add Storage Connection. Storage connection already exists. and Failed to retrieve existing storage domain information. Here's output from engine.log: http://pastebin.com/NVdzLDXb Any clues? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
can you check the engine data base for the connection? On 11/26/2013 07:12 PM, Bob Doolittle wrote: On 11/26/2013 02:00 PM, Dafna Ron wrote: can you run mount and see if you have stale connections to the domain? The only existing mounts on the Host are the loopback mount for the Data Domain, and the mount from Engine for the ISO Domain. I can import another Export domain on the same host which was created in the normal manner (and then 'destroy' it), but I can't import the converted one. -Bob On 11/26/2013 06:22 PM, Bob Doolittle wrote: Hi, I am having to recreate my engine, and want to recover my old VMs from the previous Storage Master Data Domain. A while back, Michael Ayers posted this recipe (the gmane reply feature won't allow lines longer than 80 chars, even if they were from the original post :(, so I apologize for the link ) : http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428 Should this method still work? I have tried to recreate this with 3.3.1 and can't. I copied over the old Data Domain to a new directory, and edited the dom_md/metadata file as follows: http://pastebin.com/U4xJawR8 But when I try to import it, I get: Error while executing action: Cannot add Storage Connection. Storage connection already exists. and Failed to retrieve existing storage domain information. Here's output from engine.log: http://pastebin.com/NVdzLDXb Any clues? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On 11/26/2013 03:11 PM, Dafna Ron wrote: can you check the engine data base for the connection? Sorry, will need more guidance for that :( -Bob On 11/26/2013 07:12 PM, Bob Doolittle wrote: On 11/26/2013 02:00 PM, Dafna Ron wrote: can you run mount and see if you have stale connections to the domain? The only existing mounts on the Host are the loopback mount for the Data Domain, and the mount from Engine for the ISO Domain. I can import another Export domain on the same host which was created in the normal manner (and then 'destroy' it), but I can't import the converted one. -Bob On 11/26/2013 06:22 PM, Bob Doolittle wrote: Hi, I am having to recreate my engine, and want to recover my old VMs from the previous Storage Master Data Domain. A while back, Michael Ayers posted this recipe (the gmane reply feature won't allow lines longer than 80 chars, even if they were from the original post :(, so I apologize for the link ) : http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428 Should this method still work? I have tried to recreate this with 3.3.1 and can't. I copied over the old Data Domain to a new directory, and edited the dom_md/metadata file as follows: http://pastebin.com/U4xJawR8 But when I try to import it, I get: Error while executing action: Cannot add Storage Connection. Storage connection already exists. and Failed to retrieve existing storage domain information. Here's output from engine.log: http://pastebin.com/NVdzLDXb Any clues? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
sql -U postgres engine -c 'select connection from storage_server_connections;' On 11/26/2013 08:21 PM, Bob Doolittle wrote: On 11/26/2013 03:11 PM, Dafna Ron wrote: can you check the engine data base for the connection? Sorry, will need more guidance for that :( -Bob On 11/26/2013 07:12 PM, Bob Doolittle wrote: On 11/26/2013 02:00 PM, Dafna Ron wrote: can you run mount and see if you have stale connections to the domain? The only existing mounts on the Host are the loopback mount for the Data Domain, and the mount from Engine for the ISO Domain. I can import another Export domain on the same host which was created in the normal manner (and then 'destroy' it), but I can't import the converted one. -Bob On 11/26/2013 06:22 PM, Bob Doolittle wrote: Hi, I am having to recreate my engine, and want to recover my old VMs from the previous Storage Master Data Domain. A while back, Michael Ayers posted this recipe (the gmane reply feature won't allow lines longer than 80 chars, even if they were from the original post :(, so I apologize for the link ) : http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428 Should this method still work? I have tried to recreate this with 3.3.1 and can't. I copied over the old Data Domain to a new directory, and edited the dom_md/metadata file as follows: http://pastebin.com/U4xJawR8 But when I try to import it, I get: Error while executing action: Cannot add Storage Connection. Storage connection already exists. and Failed to retrieve existing storage domain information. Here's output from engine.log: http://pastebin.com/NVdzLDXb Any clues? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On 11/26/2013 03:27 PM, Dafna Ron wrote: sql -U postgres engine -c 'select connection from storage_server_connections;' I guess you mean psql. But I keep getting an authentication error. I don't see any obvious passwords in the postgresql.conf file, nor in my setup/install logs. Is there a hardcoded password somewhere? I've tried different users - admin, postgres, engine, and I've tried all of those with the admin password I specified during setup. No dice. I also tried your offlist suggestion: psql engine postgres -c 'select connection from storage_server_connections;' with the same result: psql: FATAL: Ident authentication failed for user postgres -Bob On 11/26/2013 08:21 PM, Bob Doolittle wrote: On 11/26/2013 03:11 PM, Dafna Ron wrote: can you check the engine data base for the connection? Sorry, will need more guidance for that :( -Bob On 11/26/2013 07:12 PM, Bob Doolittle wrote: On 11/26/2013 02:00 PM, Dafna Ron wrote: can you run mount and see if you have stale connections to the domain? The only existing mounts on the Host are the loopback mount for the Data Domain, and the mount from Engine for the ISO Domain. I can import another Export domain on the same host which was created in the normal manner (and then 'destroy' it), but I can't import the converted one. -Bob On 11/26/2013 06:22 PM, Bob Doolittle wrote: Hi, I am having to recreate my engine, and want to recover my old VMs from the previous Storage Master Data Domain. A while back, Michael Ayers posted this recipe (the gmane reply feature won't allow lines longer than 80 chars, even if they were from the original post :(, so I apologize for the link ) : http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428 Should this method still work? I have tried to recreate this with 3.3.1 and can't. I copied over the old Data Domain to a new directory, and edited the dom_md/metadata file as follows: http://pastebin.com/U4xJawR8 But when I try to import it, I get: Error while executing action: Cannot add Storage Connection. Storage connection already exists. and Failed to retrieve existing storage domain information. Here's output from engine.log: http://pastebin.com/NVdzLDXb Any clues? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On Tue, Nov 26, 2013 at 10:11 PM, Bob Doolittle wrote: On 11/26/2013 03:27 PM, Dafna Ron wrote: sql -U postgres engine -c 'select connection from storage_server_connections;' I guess you mean psql. But I keep getting an authentication error. I don't see any obvious passwords in the postgresql.conf file, nor in my setup/install logs. Is there a hardcoded password somewhere? I've tried different users - admin, postgres, engine, and I've tried all of those with the admin password I specified during setup. No dice. As a workaroud possibly: - establish an ssh connection as root with the engine server - switch to postgres user [root@f18engine ~]# su - postgres - connect to engine database -bash-4.2$ psql engine psql (9.2.5) Type help for help. - execute the query engine=# select connection from storage_server_connections; connection --- f18engine.mydomain:/var/lib/exports/iso f18ovn01.mydomain:gvdata (2 rows) It work for me with 3.3.1 on f19 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
sorry Bob, di8d not notice that the p was cut from psql. the db password is always given by you during installation (you give one for admin user and one for db) you can probably see the the db and user name under /var/log/ovirt-engine/ but it should be user postgress and db engine On 11/26/2013 09:11 PM, Bob Doolittle wrote: On 11/26/2013 03:27 PM, Dafna Ron wrote: sql -U postgres engine -c 'select connection from storage_server_connections;' I guess you mean psql. But I keep getting an authentication error. I don't see any obvious passwords in the postgresql.conf file, nor in my setup/install logs. Is there a hardcoded password somewhere? I've tried different users - admin, postgres, engine, and I've tried all of those with the admin password I specified during setup. No dice. I also tried your offlist suggestion: psql engine postgres -c 'select connection from storage_server_connections;' with the same result: psql: FATAL: Ident authentication failed for user postgres -Bob On 11/26/2013 08:21 PM, Bob Doolittle wrote: On 11/26/2013 03:11 PM, Dafna Ron wrote: can you check the engine data base for the connection? Sorry, will need more guidance for that :( -Bob On 11/26/2013 07:12 PM, Bob Doolittle wrote: On 11/26/2013 02:00 PM, Dafna Ron wrote: can you run mount and see if you have stale connections to the domain? The only existing mounts on the Host are the loopback mount for the Data Domain, and the mount from Engine for the ISO Domain. I can import another Export domain on the same host which was created in the normal manner (and then 'destroy' it), but I can't import the converted one. -Bob On 11/26/2013 06:22 PM, Bob Doolittle wrote: Hi, I am having to recreate my engine, and want to recover my old VMs from the previous Storage Master Data Domain. A while back, Michael Ayers posted this recipe (the gmane reply feature won't allow lines longer than 80 chars, even if they were from the original post :(, so I apologize for the link ) : http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428 Should this method still work? I have tried to recreate this with 3.3.1 and can't. I copied over the old Data Domain to a new directory, and edited the dom_md/metadata file as follows: http://pastebin.com/U4xJawR8 But when I try to import it, I get: Error while executing action: Cannot add Storage Connection. Storage connection already exists. and Failed to retrieve existing storage domain information. Here's output from engine.log: http://pastebin.com/NVdzLDXb Any clues? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On 11/26/2013 04:25 PM, Gianluca Cecchi wrote: On Tue, Nov 26, 2013 at 10:11 PM, Bob Doolittle wrote: On 11/26/2013 03:27 PM, Dafna Ron wrote: sql -U postgres engine -c 'select connection from storage_server_connections;' I guess you mean psql. But I keep getting an authentication error. I don't see any obvious passwords in the postgresql.conf file, nor in my setup/install logs. Is there a hardcoded password somewhere? I've tried different users - admin, postgres, engine, and I've tried all of those with the admin password I specified during setup. No dice. As a workaroud possibly: - establish an ssh connection as root with the engine server - switch to postgres user [root@f18engine ~]# su - postgres - connect to engine database -bash-4.2$ psql engine psql (9.2.5) Type help for help. - execute the query engine=# select connection from storage_server_connections; connection --- f18engine.mydomain:/var/lib/exports/iso f18ovn01.mydomain:gvdata (2 rows) It work for me with 3.3.1 on f19 Brilliant, thanks! Yes this works, and produces: engine=# select connection from storage_server_connections; connection - ovirt-vm.smartcity.net:/var/lib/exports/iso 172.16.0.58:/export/VM_EXPORTDOMAIN 172.16.0.58:/export/VM_DATADOMAIN (3 rows) So that's strange - the /export/VM_EXPORTDOMAIN is in fact the export domain I am trying (and failing) to import. Note that the first time I tried this it failed, because of a firewall running on the Host. I wonder if that left some bad state in the DB. So, is there some way I can clear this out? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On Tue, Nov 26, 2013 at 10:28 PM, Dafna Ron wrote: sorry Bob, di8d not notice that the p was cut from psql. the db password is always given by you during installation (you give one for admin user and one for db) you can probably see the the db and user name under /var/log/ovirt-engine/ but it should be user postgress and db engine Actually you have the option to select [Automatic] for db configuration during install. SO in this case possibly it is hardcoded/randomized? See my log for example 2013-10-03 11:20:06 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND --== DATABASE CONFIGURATION ==- - 2013-10-03 11:20:06 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND 2013-10-03 11:20:06 DEBUG otopi.context context._executeMethod:123 Stage customization METHOD otopi.plugins.ovirt_engine_setup.provisioning.p ostgres.Plugin._customization 2013-10-03 11:20:06 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND Where is the database located? (Local, Remote) [Local]: 2013-10-03 11:20:19 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND Setup can configure the local p ostgresql server automatically for the engine to run. This may conflict with existing applications. 2013-10-03 11:20:19 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND Would you like Setup to automat ically configure postgresql, or prefer to perform that manually? (Automatic, Manual) [Automatic]: Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On 11/26/2013 03:27 PM, Dafna Ron wrote: sql -U postgres engine -c 'select connection from storage_server_connections;' So now that we determined that I have stale connection state in my DB, any suggestions as to how I might clear it out safely? I tried rebooting my Engine, but the connection is still in the DB and it still doesn't show in the Admin Portal. Thanks, Bob On 11/26/2013 08:21 PM, Bob Doolittle wrote: On 11/26/2013 03:11 PM, Dafna Ron wrote: can you check the engine data base for the connection? Sorry, will need more guidance for that :( -Bob On 11/26/2013 07:12 PM, Bob Doolittle wrote: On 11/26/2013 02:00 PM, Dafna Ron wrote: can you run mount and see if you have stale connections to the domain? The only existing mounts on the Host are the loopback mount for the Data Domain, and the mount from Engine for the ISO Domain. I can import another Export domain on the same host which was created in the normal manner (and then 'destroy' it), but I can't import the converted one. -Bob On 11/26/2013 06:22 PM, Bob Doolittle wrote: Hi, I am having to recreate my engine, and want to recover my old VMs from the previous Storage Master Data Domain. A while back, Michael Ayers posted this recipe (the gmane reply feature won't allow lines longer than 80 chars, even if they were from the original post :(, so I apologize for the link ) : http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428 Should this method still work? I have tried to recreate this with 3.3.1 and can't. I copied over the old Data Domain to a new directory, and edited the dom_md/metadata file as follows: http://pastebin.com/U4xJawR8 But when I try to import it, I get: Error while executing action: Cannot add Storage Connection. Storage connection already exists. and Failed to retrieve existing storage domain information. Here's output from engine.log: http://pastebin.com/NVdzLDXb Any clues? Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
Thanks for this. I'm on the Dreyou version and hope that I can update to this at the moment. 2013/3/1 Itamar Heim ih...@redhat.com On 01/03/2013 10:40, Matt . wrote: I have tried this with a domain that was not master and I can import it. Strange is that all tabs, also the VM's that I would like to import, are empty. What could be the reason for this ? Thanks, Matt __**_ Users mailing list Users@ovirt.org http://lists.ovirt.org/**mailman/listinfo/usershttp://lists.ovirt.org/mailman/listinfo/users only master domain has the OVF files on it which would appear as VMs in the import tab. this trick doesn't work with non master domains... hopefully, now that there is a patch to detect and register orphan disks, you can use it instead (by having these disks moved to a data domain, then registering them in the engine). (now == post 3.2, so you would need a patched or nightly version + this was merged earlier this week, so very young) ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On 11/01/2012 03:01 AM, Dead Horse wrote: This is good info. Given that the metadata can be edited is there a way to redesignate which storage domain should be the master? I have run into a couple of times in which for various reasons the master domain could not be reached and another storage domain was elected as master. Is there a way to force an election or edit the metadata to redesignate the original master domain back as master again? i heartly suggest to not try and mess with that on your own. you can move other storage domains to maint, to force engine to reconstruct the master on another domain. (again, do *not* do it on your own via metadata) - DHC On Wed, Oct 31, 2012 at 12:43 PM, Itamar Heim ih...@redhat.com mailto:ih...@redhat.com wrote: On 10/31/2012 07:36 PM, Simon Grinberg wrote: - Original Message - From: Itamar Heim ih...@redhat.com mailto:ih...@redhat.com To: Michael Ayers ayer...@redhat.com mailto:ayer...@redhat.com Cc: users@ovirt.org mailto:users@ovirt.org Sent: Tuesday, October 30, 2012 10:57:52 PM Subject: Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain On 10/30/2012 09:29 PM, Michael Ayers wrote: Hey All, I ran into this issue myself where I needed to convert a data domain to an export domain in order to recover virtual guests from a corrupted ovirt/rhevm instance into a new ovirt/rhevm instance. This wasn’t documented anywhere that I saw but with the help of Itamar Heim and an well timed email to the list from Igor Lvovsky last night I was able to do this and wanted to send to the list a documented procedure for how to modify the metadata of the data domain prior to import as an export domain. This procedure works for both RHEV-M and Ovirt. Let me know if you have any questions. glad it worked. Will this work if the recovered storage domain was not the master? no. only for nfs storage domain, only if it was master. care to wikify for others? thanks, Itamar Original Data Domain Metadata File --__ CLASS=Data DESCRIPTION=vm-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool POOL_DOMAINS=dd8bc200-6e28-__4185-bfe0-f0affb94f283:Active,__ddefdf6c-ef68-419c-9f72-__76d27bf7d788:Active,66b3b243-__6cc6-465f-b130-6f2cd0b70514:__Active POOL_SPM_ID=2 POOL_SPM_LVER=17 POOL_UUID=a207f052-f4bf-44a3-__b637-c6d2020a7c41 REMOTE_PATH=nfsserver:/ovirt/__vm-storage ROLE=Master SDUUID=66b3b243-6cc6-465f-__b130-6f2cd0b70514 TYPE=NFS VERSION=0 _SHA_CKSUM=__009fa538321ac56749669127f43cc7__54aa59d398 Diff between Original DD Metadata File and ED Metadata File --__ --- metadata-data-storage 2012-10-30 12:24:52.484006958 -0700 +++ metadata-exp-storage2012-10-30 12:14:59.043807789 -0700 @@ -1,5 +1,5 @@ -CLASS=Data -DESCRIPTION=vm-storage +CLASS=Backup +DESCRIPTION=export-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 @@ -7,13 +7,12 @@ LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool -POOL_DOMAINS=dd8bc200-6e28-__4185-bfe0-f0affb94f283:Active,__ddefdf6c-ef68-419c-9f72-__76d27bf7d788:Active,66b3b243-__6cc6-465f-b130-6f2cd0b70514:__Active +POOL_DOMAINS= POOL_SPM_ID=2 POOL_SPM_LVER=17 -POOL_UUID=a207f052-f4bf-44a3-__b637-c6d2020a7c41 -REMOTE_PATH=nfsserver:/ovirt/__vm-storage -ROLE=Master +POOL_UUID= +REMOTE_PATH=nfsserver:/ovirt/__export-storage +ROLE=Regular SDUUID=66b3b243-6cc6-465f-__b130-6f2cd0b70514 TYPE=NFS
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
Itamar, I concur with you. I am aware of the dangers here (I edited metadata once already to test recovering a storage domain in a test setup). It took me a few tries and looking through the code that generate and manipulates that data to get it right. However perhaps as a feature request it would be prudent to allow for the ability to choose or change which domain is the master without taking down all the other domains. If you have a-lot of domains this really becomes problematic to play musical chairs with the domains to get the one you want to be master elected. This also requires you to take down VM's which makes it even more problematic. Can we get a make this domain the master feature added to the UI/Cli? -DHC On Thu, Nov 1, 2012 at 2:07 AM, Itamar Heim ih...@redhat.com wrote: On 11/01/2012 03:01 AM, Dead Horse wrote: This is good info. Given that the metadata can be edited is there a way to redesignate which storage domain should be the master? I have run into a couple of times in which for various reasons the master domain could not be reached and another storage domain was elected as master. Is there a way to force an election or edit the metadata to redesignate the original master domain back as master again? i heartly suggest to not try and mess with that on your own. you can move other storage domains to maint, to force engine to reconstruct the master on another domain. (again, do *not* do it on your own via metadata) - DHC On Wed, Oct 31, 2012 at 12:43 PM, Itamar Heim ih...@redhat.com mailto:ih...@redhat.com wrote: On 10/31/2012 07:36 PM, Simon Grinberg wrote: - Original Message - From: Itamar Heim ih...@redhat.com mailto: ih...@redhat.com To: Michael Ayers ayer...@redhat.com mailto:ayer...@redhat.com Cc: users@ovirt.org mailto:users@ovirt.org Sent: Tuesday, October 30, 2012 10:57:52 PM Subject: Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain On 10/30/2012 09:29 PM, Michael Ayers wrote: Hey All, I ran into this issue myself where I needed to convert a data domain to an export domain in order to recover virtual guests from a corrupted ovirt/rhevm instance into a new ovirt/rhevm instance. This wasn’t documented anywhere that I saw but with the help of Itamar Heim and an well timed email to the list from Igor Lvovsky last night I was able to do this and wanted to send to the list a documented procedure for how to modify the metadata of the data domain prior to import as an export domain. This procedure works for both RHEV-M and Ovirt. Let me know if you have any questions. glad it worked. Will this work if the recovered storage domain was not the master? no. only for nfs storage domain, only if it was master. care to wikify for others? thanks, Itamar Original Data Domain Metadata File --**__ CLASS=Data DESCRIPTION=vm-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool POOL_DOMAINS=dd8bc200-6e28-__** 4185-bfe0-f0affb94f283:Active,**__ddefdf6c-ef68-419c-9f72-__** 76d27bf7d788:Active,66b3b243-_**_6cc6-465f-b130-6f2cd0b70514:_**_Active POOL_SPM_ID=2 POOL_SPM_LVER=17 POOL_UUID=a207f052-f4bf-44a3-_**_b637-c6d2020a7c41 REMOTE_PATH=nfsserver:/ovirt/_**_vm-storage ROLE=Master SDUUID=66b3b243-6cc6-465f-__**b130-6f2cd0b70514 TYPE=NFS VERSION=0 _SHA_CKSUM=__**009fa538321ac56749669127f43cc7** __54aa59d398 Diff between Original DD Metadata File and ED Metadata File --**__ --- metadata-data-storage 2012-10-30 12:24:52.484006958 -0700 +++ metadata-exp-storage2012-10-30 12:14:59.043807789 -0700 @@ -1,5 +1,5 @@ -CLASS=Data -DESCRIPTION=vm-storage +CLASS=Backup +DESCRIPTION=export-storage
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On 11/01/2012 04:45 PM, Dead Horse wrote: Itamar, I concur with you. I am aware of the dangers here (I edited metadata once already to test recovering a storage domain in a test setup). It took me a few tries and looking through the code that generate and manipulates that data to get it right. However perhaps as a feature request it would be prudent to allow for the ability to choose or change which domain is the master without taking down all the other domains. If you have a-lot of domains this really becomes problematic to play musical chairs with the domains to get the one you want to be master elected. This also requires you to take down VM's which makes it even more problematic. Can we get a make this domain the master feature added to the UI/Cli? the plan is to remove the need for a master domain to begin with (SDM feature) -DHC On Thu, Nov 1, 2012 at 2:07 AM, Itamar Heim ih...@redhat.com mailto:ih...@redhat.com wrote: On 11/01/2012 03:01 AM, Dead Horse wrote: This is good info. Given that the metadata can be edited is there a way to redesignate which storage domain should be the master? I have run into a couple of times in which for various reasons the master domain could not be reached and another storage domain was elected as master. Is there a way to force an election or edit the metadata to redesignate the original master domain back as master again? i heartly suggest to not try and mess with that on your own. you can move other storage domains to maint, to force engine to reconstruct the master on another domain. (again, do *not* do it on your own via metadata) - DHC On Wed, Oct 31, 2012 at 12:43 PM, Itamar Heim ih...@redhat.com mailto:ih...@redhat.com mailto:ih...@redhat.com mailto:ih...@redhat.com wrote: On 10/31/2012 07:36 PM, Simon Grinberg wrote: - Original Message - From: Itamar Heim ih...@redhat.com mailto:ih...@redhat.com mailto:ih...@redhat.com mailto:ih...@redhat.com To: Michael Ayers ayer...@redhat.com mailto:ayer...@redhat.com mailto:ayer...@redhat.com mailto:ayer...@redhat.com Cc: users@ovirt.org mailto:users@ovirt.org mailto:users@ovirt.org mailto:users@ovirt.org Sent: Tuesday, October 30, 2012 10:57:52 PM Subject: Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain On 10/30/2012 09:29 PM, Michael Ayers wrote: Hey All, I ran into this issue myself where I needed to convert a data domain to an export domain in order to recover virtual guests from a corrupted ovirt/rhevm instance into a new ovirt/rhevm instance. This wasn’t documented anywhere that I saw but with the help of Itamar Heim and an well timed email to the list from Igor Lvovsky last night I was able to do this and wanted to send to the list a documented procedure for how to modify the metadata of the data domain prior to import as an export domain. This procedure works for both RHEV-M and Ovirt. Let me know if you have any questions. glad it worked. Will this work if the recovered storage domain was not the master? no. only for nfs storage domain, only if it was master. care to wikify for others? thanks, Itamar Original Data Domain Metadata File -- CLASS=Data DESCRIPTION=vm-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool POOL_DOMAINS=dd8bc200-6e28-4185-bfe0-f0affb94f283:Active,ddefdf6c-ef68-419c-9f72-76d27bf7d788:Active,66b3b243-6cc6-465f-b130-6f2cd0b70514:Active POOL_SPM_ID=2
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
Even better ;) I thought I saw mention on the mailing lists of some notion of storage domain import/export is that also in the works? On Thu, Nov 1, 2012 at 9:47 AM, Itamar Heim ih...@redhat.com wrote: On 11/01/2012 04:45 PM, Dead Horse wrote: Itamar, I concur with you. I am aware of the dangers here (I edited metadata once already to test recovering a storage domain in a test setup). It took me a few tries and looking through the code that generate and manipulates that data to get it right. However perhaps as a feature request it would be prudent to allow for the ability to choose or change which domain is the master without taking down all the other domains. If you have a-lot of domains this really becomes problematic to play musical chairs with the domains to get the one you want to be master elected. This also requires you to take down VM's which makes it even more problematic. Can we get a make this domain the master feature added to the UI/Cli? the plan is to remove the need for a master domain to begin with (SDM feature) -DHC On Thu, Nov 1, 2012 at 2:07 AM, Itamar Heim ih...@redhat.com mailto:ih...@redhat.com wrote: On 11/01/2012 03:01 AM, Dead Horse wrote: This is good info. Given that the metadata can be edited is there a way to redesignate which storage domain should be the master? I have run into a couple of times in which for various reasons the master domain could not be reached and another storage domain was elected as master. Is there a way to force an election or edit the metadata to redesignate the original master domain back as master again? i heartly suggest to not try and mess with that on your own. you can move other storage domains to maint, to force engine to reconstruct the master on another domain. (again, do *not* do it on your own via metadata) - DHC On Wed, Oct 31, 2012 at 12:43 PM, Itamar Heim ih...@redhat.com mailto:ih...@redhat.com mailto:ih...@redhat.com mailto:ih...@redhat.com wrote: On 10/31/2012 07:36 PM, Simon Grinberg wrote: - Original Message - From: Itamar Heim ih...@redhat.com mailto:ih...@redhat.com mailto:ih...@redhat.com mailto:ih...@redhat.com To: Michael Ayers ayer...@redhat.com mailto:ayer...@redhat.com mailto:ayer...@redhat.com mailto:ayer...@redhat.com Cc: users@ovirt.org mailto:users@ovirt.org mailto:users@ovirt.org mailto:users@ovirt.org Sent: Tuesday, October 30, 2012 10:57:52 PM Subject: Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain On 10/30/2012 09:29 PM, Michael Ayers wrote: Hey All, I ran into this issue myself where I needed to convert a data domain to an export domain in order to recover virtual guests from a corrupted ovirt/rhevm instance into a new ovirt/rhevm instance. This wasn’t documented anywhere that I saw but with the help of Itamar Heim and an well timed email to the list from Igor Lvovsky last night I was able to do this and wanted to send to the list a documented procedure for how to modify the metadata of the data domain prior to import as an export domain. This procedure works for both RHEV-M and Ovirt. Let me know if you have any questions. glad it worked. Will this work if the recovered storage domain was not the master? no. only for nfs storage domain, only if it was master. care to wikify for others? thanks, Itamar Original Data Domain Metadata File --** CLASS=Data DESCRIPTION=vm-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
- Original Message - From: Itamar Heim ih...@redhat.com To: Michael Ayers ayer...@redhat.com Cc: users@ovirt.org Sent: Tuesday, October 30, 2012 10:57:52 PM Subject: Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain On 10/30/2012 09:29 PM, Michael Ayers wrote: Hey All, I ran into this issue myself where I needed to convert a data domain to an export domain in order to recover virtual guests from a corrupted ovirt/rhevm instance into a new ovirt/rhevm instance. This wasn’t documented anywhere that I saw but with the help of Itamar Heim and an well timed email to the list from Igor Lvovsky last night I was able to do this and wanted to send to the list a documented procedure for how to modify the metadata of the data domain prior to import as an export domain. This procedure works for both RHEV-M and Ovirt. Let me know if you have any questions. glad it worked. Will this work if the recovered storage domain was not the master? care to wikify for others? thanks, Itamar Original Data Domain Metadata File -- CLASS=Data DESCRIPTION=vm-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool POOL_DOMAINS=dd8bc200-6e28-4185-bfe0-f0affb94f283:Active,ddefdf6c-ef68-419c-9f72-76d27bf7d788:Active,66b3b243-6cc6-465f-b130-6f2cd0b70514:Active POOL_SPM_ID=2 POOL_SPM_LVER=17 POOL_UUID=a207f052-f4bf-44a3-b637-c6d2020a7c41 REMOTE_PATH=nfsserver:/ovirt/vm-storage ROLE=Master SDUUID=66b3b243-6cc6-465f-b130-6f2cd0b70514 TYPE=NFS VERSION=0 _SHA_CKSUM=009fa538321ac56749669127f43cc754aa59d398 Diff between Original DD Metadata File and ED Metadata File -- --- metadata-data-storage 2012-10-30 12:24:52.484006958 -0700 +++ metadata-exp-storage2012-10-30 12:14:59.043807789 -0700 @@ -1,5 +1,5 @@ -CLASS=Data -DESCRIPTION=vm-storage +CLASS=Backup +DESCRIPTION=export-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 @@ -7,13 +7,12 @@ LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool -POOL_DOMAINS=dd8bc200-6e28-4185-bfe0-f0affb94f283:Active,ddefdf6c-ef68-419c-9f72-76d27bf7d788:Active,66b3b243-6cc6-465f-b130-6f2cd0b70514:Active +POOL_DOMAINS= POOL_SPM_ID=2 POOL_SPM_LVER=17 -POOL_UUID=a207f052-f4bf-44a3-b637-c6d2020a7c41 -REMOTE_PATH=nfsserver:/ovirt/vm-storage -ROLE=Master +POOL_UUID= +REMOTE_PATH=nfsserver:/ovirt/export-storage +ROLE=Regular SDUUID=66b3b243-6cc6-465f-b130-6f2cd0b70514 TYPE=NFS VERSION=0 -_SHA_CKSUM=009fa538321ac56749669127f43cc754aa59d398 Thanks, Michael - Michael J. Ayers Red Hat Inc. Solutions Architect e: ayer...@redhat.com mailto:ayer...@redhat.com w: www.redhat.com http://www.redhat.com/ ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On 10/31/2012 07:36 PM, Simon Grinberg wrote: - Original Message - From: Itamar Heim ih...@redhat.com To: Michael Ayers ayer...@redhat.com Cc: users@ovirt.org Sent: Tuesday, October 30, 2012 10:57:52 PM Subject: Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain On 10/30/2012 09:29 PM, Michael Ayers wrote: Hey All, I ran into this issue myself where I needed to convert a data domain to an export domain in order to recover virtual guests from a corrupted ovirt/rhevm instance into a new ovirt/rhevm instance. This wasn’t documented anywhere that I saw but with the help of Itamar Heim and an well timed email to the list from Igor Lvovsky last night I was able to do this and wanted to send to the list a documented procedure for how to modify the metadata of the data domain prior to import as an export domain. This procedure works for both RHEV-M and Ovirt. Let me know if you have any questions. glad it worked. Will this work if the recovered storage domain was not the master? no. only for nfs storage domain, only if it was master. care to wikify for others? thanks, Itamar Original Data Domain Metadata File -- CLASS=Data DESCRIPTION=vm-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool POOL_DOMAINS=dd8bc200-6e28-4185-bfe0-f0affb94f283:Active,ddefdf6c-ef68-419c-9f72-76d27bf7d788:Active,66b3b243-6cc6-465f-b130-6f2cd0b70514:Active POOL_SPM_ID=2 POOL_SPM_LVER=17 POOL_UUID=a207f052-f4bf-44a3-b637-c6d2020a7c41 REMOTE_PATH=nfsserver:/ovirt/vm-storage ROLE=Master SDUUID=66b3b243-6cc6-465f-b130-6f2cd0b70514 TYPE=NFS VERSION=0 _SHA_CKSUM=009fa538321ac56749669127f43cc754aa59d398 Diff between Original DD Metadata File and ED Metadata File -- --- metadata-data-storage 2012-10-30 12:24:52.484006958 -0700 +++ metadata-exp-storage2012-10-30 12:14:59.043807789 -0700 @@ -1,5 +1,5 @@ -CLASS=Data -DESCRIPTION=vm-storage +CLASS=Backup +DESCRIPTION=export-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 @@ -7,13 +7,12 @@ LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool -POOL_DOMAINS=dd8bc200-6e28-4185-bfe0-f0affb94f283:Active,ddefdf6c-ef68-419c-9f72-76d27bf7d788:Active,66b3b243-6cc6-465f-b130-6f2cd0b70514:Active +POOL_DOMAINS= POOL_SPM_ID=2 POOL_SPM_LVER=17 -POOL_UUID=a207f052-f4bf-44a3-b637-c6d2020a7c41 -REMOTE_PATH=nfsserver:/ovirt/vm-storage -ROLE=Master +POOL_UUID= +REMOTE_PATH=nfsserver:/ovirt/export-storage +ROLE=Regular SDUUID=66b3b243-6cc6-465f-b130-6f2cd0b70514 TYPE=NFS VERSION=0 -_SHA_CKSUM=009fa538321ac56749669127f43cc754aa59d398 Thanks, Michael - Michael J. Ayers Red Hat Inc. Solutions Architect e: ayer...@redhat.com mailto:ayer...@redhat.com w: www.redhat.com http://www.redhat.com/ ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
This is good info. Given that the metadata can be edited is there a way to redesignate which storage domain should be the master? I have run into a couple of times in which for various reasons the master domain could not be reached and another storage domain was elected as master. Is there a way to force an election or edit the metadata to redesignate the original master domain back as master again? - DHC On Wed, Oct 31, 2012 at 12:43 PM, Itamar Heim ih...@redhat.com wrote: On 10/31/2012 07:36 PM, Simon Grinberg wrote: - Original Message - From: Itamar Heim ih...@redhat.com To: Michael Ayers ayer...@redhat.com Cc: users@ovirt.org Sent: Tuesday, October 30, 2012 10:57:52 PM Subject: Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain On 10/30/2012 09:29 PM, Michael Ayers wrote: Hey All, I ran into this issue myself where I needed to convert a data domain to an export domain in order to recover virtual guests from a corrupted ovirt/rhevm instance into a new ovirt/rhevm instance. This wasn’t documented anywhere that I saw but with the help of Itamar Heim and an well timed email to the list from Igor Lvovsky last night I was able to do this and wanted to send to the list a documented procedure for how to modify the metadata of the data domain prior to import as an export domain. This procedure works for both RHEV-M and Ovirt. Let me know if you have any questions. glad it worked. Will this work if the recovered storage domain was not the master? no. only for nfs storage domain, only if it was master. care to wikify for others? thanks, Itamar Original Data Domain Metadata File --** CLASS=Data DESCRIPTION=vm-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool POOL_DOMAINS=dd8bc200-6e28-**4185-bfe0-f0affb94f283:Active,** ddefdf6c-ef68-419c-9f72-**76d27bf7d788:Active,66b3b243-** 6cc6-465f-b130-6f2cd0b70514:**Active POOL_SPM_ID=2 POOL_SPM_LVER=17 POOL_UUID=a207f052-f4bf-44a3-**b637-c6d2020a7c41 REMOTE_PATH=nfsserver:/ovirt/**vm-storage ROLE=Master SDUUID=66b3b243-6cc6-465f-**b130-6f2cd0b70514 TYPE=NFS VERSION=0 _SHA_CKSUM=**009fa538321ac56749669127f43cc7**54aa59d398 Diff between Original DD Metadata File and ED Metadata File --** --- metadata-data-storage 2012-10-30 12:24:52.484006958 -0700 +++ metadata-exp-storage2012-10-30 12:14:59.043807789 -0700 @@ -1,5 +1,5 @@ -CLASS=Data -DESCRIPTION=vm-storage +CLASS=Backup +DESCRIPTION=export-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 @@ -7,13 +7,12 @@ LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool -POOL_DOMAINS=dd8bc200-6e28-**4185-bfe0-f0affb94f283:Active,** ddefdf6c-ef68-419c-9f72-**76d27bf7d788:Active,66b3b243-** 6cc6-465f-b130-6f2cd0b70514:**Active +POOL_DOMAINS= POOL_SPM_ID=2 POOL_SPM_LVER=17 -POOL_UUID=a207f052-f4bf-44a3-**b637-c6d2020a7c41 -REMOTE_PATH=nfsserver:/ovirt/**vm-storage -ROLE=Master +POOL_UUID= +REMOTE_PATH=nfsserver:/ovirt/**export-storage +ROLE=Regular SDUUID=66b3b243-6cc6-465f-**b130-6f2cd0b70514 TYPE=NFS VERSION=0 -_SHA_CKSUM=**009fa538321ac56749669127f43cc7**54aa59d398 Thanks, Michael --**--- Michael J. Ayers Red Hat Inc. Solutions Architect e: ayer...@redhat.com mailto:ayer...@redhat.com w: www.redhat.com http://www.redhat.com/ __**_ Users mailing list Users@ovirt.org http://lists.ovirt.org/**mailman/listinfo/usershttp://lists.ovirt.org/mailman/listinfo/users __**_ Users mailing list Users@ovirt.org http://lists.ovirt.org/**mailman/listinfo/usershttp://lists.ovirt.org/mailman/listinfo/users __**_ Users mailing list Users@ovirt.org http://lists.ovirt.org/**mailman/listinfo/usershttp://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Documentation: Storage Domain conversion from Data Domain to Export Domain
On 10/30/2012 09:29 PM, Michael Ayers wrote: Hey All, I ran into this issue myself where I needed to convert a data domain to an export domain in order to recover virtual guests from a corrupted ovirt/rhevm instance into a new ovirt/rhevm instance. This wasn’t documented anywhere that I saw but with the help of Itamar Heim and an well timed email to the list from Igor Lvovsky last night I was able to do this and wanted to send to the list a documented procedure for how to modify the metadata of the data domain prior to import as an export domain. This procedure works for both RHEV-M and Ovirt. Let me know if you have any questions. glad it worked. care to wikify for others? thanks, Itamar Original Data Domain Metadata File -- CLASS=Data DESCRIPTION=vm-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool POOL_DOMAINS=dd8bc200-6e28-4185-bfe0-f0affb94f283:Active,ddefdf6c-ef68-419c-9f72-76d27bf7d788:Active,66b3b243-6cc6-465f-b130-6f2cd0b70514:Active POOL_SPM_ID=2 POOL_SPM_LVER=17 POOL_UUID=a207f052-f4bf-44a3-b637-c6d2020a7c41 REMOTE_PATH=nfsserver:/ovirt/vm-storage ROLE=Master SDUUID=66b3b243-6cc6-465f-b130-6f2cd0b70514 TYPE=NFS VERSION=0 _SHA_CKSUM=009fa538321ac56749669127f43cc754aa59d398 Diff between Original DD Metadata File and ED Metadata File -- --- metadata-data-storage 2012-10-30 12:24:52.484006958 -0700 +++ metadata-exp-storage2012-10-30 12:14:59.043807789 -0700 @@ -1,5 +1,5 @@ -CLASS=Data -DESCRIPTION=vm-storage +CLASS=Backup +DESCRIPTION=export-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 @@ -7,13 +7,12 @@ LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=2 POOL_DESCRIPTION=MyPool -POOL_DOMAINS=dd8bc200-6e28-4185-bfe0-f0affb94f283:Active,ddefdf6c-ef68-419c-9f72-76d27bf7d788:Active,66b3b243-6cc6-465f-b130-6f2cd0b70514:Active +POOL_DOMAINS= POOL_SPM_ID=2 POOL_SPM_LVER=17 -POOL_UUID=a207f052-f4bf-44a3-b637-c6d2020a7c41 -REMOTE_PATH=nfsserver:/ovirt/vm-storage -ROLE=Master +POOL_UUID= +REMOTE_PATH=nfsserver:/ovirt/export-storage +ROLE=Regular SDUUID=66b3b243-6cc6-465f-b130-6f2cd0b70514 TYPE=NFS VERSION=0 -_SHA_CKSUM=009fa538321ac56749669127f43cc754aa59d398 Thanks, Michael - Michael J. Ayers Red Hat Inc. Solutions Architect e: ayer...@redhat.com mailto:ayer...@redhat.com w: www.redhat.com http://www.redhat.com/ ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
