Re: [Users] GSoC 14 Idea Discussion - virt-sparsify integration
- Original Message - From: Utkarsh Singh utkarshs...@gmail.com To: users@ovirt.org Sent: Friday, March 7, 2014 7:23:16 PM Subject: [Users] GSoC 14 Idea Discussion - virt-sparsify integration Hello, I am Utkarsh, a 4th year undergrad from IIT Delhi and a GSoC-14 aspirant. I have been lately involved in an ongoing project Baadal Cloud Computing Platform in my institute, which has got me interested in oVirt for a potential GSoC project. I was going through the virt-sparsify integration project idea. I have gone through the architecture documentation on the oVirt website. As far as I understand, the virt-sparsify integration needs to be done on the VDSM daemon, and it's control is either going to be completely independent of ovirt-engine (for example running it once every 24 hours), or it's something that is centrally controlled by the ovirt-engine through XML/RPC calls. The details are not specified in the project ideas page. I would like to ask - 1. What would be the proposed ideal implementation? (Central-Control or Independent-Control) 2. Is virt-sparsify usage going to be automated or administrator-triggered, or a combination of both? There are some aspects of the idea, which I would like to discuss before I start working on a proposal. It's not necessary that an automated usage of virt-sparsify is limited to any simple idea. Architecture documentation states that ovirt-engine has features like Monitoring that would allow administrators (and possibly users) to be aware of vm-guest performance as well as vm-host performance. I am not very sure about how this data is collected, Is it done through MoM, or Is this directly done by VDSM, or is someone else doing this (for hosts). It would be great if someone can explain that to me. This information about vm-guest usage and vm-host health can help in determining how virt-sparsify is to be used. I am also not very clear about the Shared Storage component in the architecture. Does oVirt make any assumptions about the Shared Storage. For example, the performance difference between running virt-sparsify on NFS as compared to running it (if possible) directly on storage hardware. If the Storage solution is necessarily a NAS instance, then virt-sparsify on NFS mount is the only option. Right now, I am in the process of setting up oVirt on my system, and getting more familiar with the architecture. Regarding my experience. I am acquainted with both Java and Python. I have little experience with JBoss, but I have worked on some other Web Application Servers like web2py and Play Framework. My involvement in Baadal Platform has got me acquainted with libvirt/QEMU, the details of which I have mentioned below (if anyone is interested). Please advise me about the things that I am missing about this project. If there are some implementation details that I need to know, kindly help me with that too. Looking forward. Thanks. = Utkarsh IIT Delhi Ongoing project details - Article (Old) http://www.cc.iitd.ernet.in/CSC/index.php?view=articleid=123:baadal-the-iitd-computing-cloud Github https://github.com/apoorvemohan/newbaadal My contribution - Deployment Scripting and Sandbox Environment Setup for Testing https://github.com/apoorvemohan/newbaadal/tree/master/baadaltesting/sandbox ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users (Adding vdsm-devel and engine-devel) -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [oVirt Test Day 3] oVirt live
- Original Message - From: Einav Cohen eco...@redhat.com To: users users@ovirt.org Sent: Friday, March 7, 2014 1:24:08 AM Subject: [Users] [oVirt Test Day 3] oVirt live based on [1]: I took the latest (actually, only) ovirt live iso from: http://jenkins.ovirt.org/view/All/job/ovirt_live_create_iso/ [http://i.imgur.com/o639iU7.png] After running the iso (more details to follow), it turns out that this is a 3.5.0/master iso. [http://i.imgur.com/OSO14tu.png] Google'ing 'ovirt live' didn't bring any 3.4 related results. I found the GitHub which doesn't seem to have a 3.4 branch [http://i.imgur.com/hrsq5ps.png] and the wiki page [2] that the latest iso in it seems to be an October 2013 one, which AFAIK is of ovirt-3.3. details on running the ovirt 3.5.0/master live iso: I used the 'VM' method. I used a virt-manager VM on an already well-configured physical machine, so I skipped the instructions in the 'VM' section [3]. As the ISO seemed to be targeted at el6, I chose in virt-manager to create a RHEL 6 machine, which is the closest thing to el6 that I could find in virt-manager options. (no CentOS option in virt-manager, as far as I could see) [http://i.imgur.com/fQGGwXK.png] [ignore the 3.4 in the name of the ISO - that's just the name that I gave to the ISO file since I wrongfully thought that it is a 3.4 one] To allow the VM to function as a hypervisor, I copied the physical CPU configuration to the VM (which should include the virtualization-enabled stuff, AFAIK). [http://i.imgur.com/JHWwWkp.png] [I successfully created virtual Hosts a lot of times, so I know the way to create the VM as I detailed above should work properly] running the oVirt Live image started off smoothly, problem encountered when attempting to activate VDSM. after waiting a lot of time for VDSM to activate, the installation finally gave up. [http://i.imgur.com/tTotnNB.png] Happened to me too (also while testing oVirt live during the test day). /var/log/vdsm/vdsm.log was empty and owned by root:root. This makes me think that the reason is [1]. The image I (and I guess you too) used was built on Mar 5, as you said it was built from nightly repos, but wrongly used the old nightly repo (prior to the introduction of /pub/snapshot*). So it included a somewhat older vdsm - iirc nightly of Feb 26 or so. I was pretty certain that the vdsm logs issue was solved in master/nightly much before that, but I might be wrong - [1] points at a lot of changes and I didn't check all of them. It was moved to ON_QA on Feb 4. I told Ohad about this and he'll hopefully soon point the ovirt-live build at the new nightly repos. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1055153 -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Reimporting storage domains after reinstalling ovirt
Hi Boudewijn, First of all, the wiki page you are referring to is a feature page that was never implemented. We are currently working on the same feature, this is the correct feature page: http://www.ovirt.org/Features/ImportStorageDomain . I will ask that the irrelevant page be removed to avoid any further confusion. Second, currently, the only way to import a domain is to create an export domain and import it. Can you get the old setup-up and create an export domain? If not, we'll try to help and work around this is issue, but this is going to be very complex, since this is not supported. Just to have a general understanding of your setup - your storage on the same machine as ovirt engine? I'm assuming you're using web-admin. What exactly are you doing there? We don't have the import option there as you mentioned, so I don't understand how you could import an SD that was not export. Adding the entry to /etc/exports is meaningless. Do you have the ovfs of the old VMs available? In the meantime checking for an easier solution than the above, will get back to you on that. Regards, Vered - Original Message - From: Boudewijn Ector boudew...@boudewijnector.nl To: users@ovirt.org Sent: Sunday, March 9, 2014 3:48:41 AM Subject: Re: [Users] Reimporting storage domains after reinstalling ovirt On 09-03-14 02:12, Boudewijn Ector wrote: Hi Guys, Currently I've got a Centos machine running the latest ovirt-release. This machine is using a local raid set containing a directory with ovirt-based VMs from my previous install. The ovirt install is a completely fresh install, no storage/VMs have been created yet. What's the best way to reimport those? I might try to create a new storage domain and copy all old VMs into it (if that works anyway...) , or just reimport the old domain from the web-interface. Does either trick have any advantage, or is there a best practice I should adhere to? Cheers, Boudewijn ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users I just tried reimporting my old storage domains but that doesn't seem to work: [root@server data]# pwd /raid/ovirt-old/data [root@server data]# ls 1979444d-b79a-494c-8c1a-bcc132e31a04 __DIRECT_IO_TEST__ This is the old data domain I used, and the 1979444d-b79a-494c-8c1a-bcc132e31a04 contains quite a lot of VMs. When going to the webinterface and doing : - Storage - Import domain - Type: NFS - export path: $IP:/raid/ovirt-old/data (and $IP:/raid/ovirt-old/data/1979444d-b79a-494c-8c1a-bcc132e31a04) Of course I created an entry in /etc/exports in order to be able to mount this domain by NFS: [root@leiden data]# exportfs /raid/ovirt 192.168.1.44/255.255.255.255 /raid/ovirt-old 192.168.1.44/255.255.255.255 And ownership is by user vdsm. Despite of this it doesn't work. Unfortunately this page (http://www.ovirt.org/Features/Import_an_existing_Storage_Domain) isn't of much use either. How should I do this? Cheers, Boudewijn ___ 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] How to get status of async operation via Java SDK
Juan, can you provide some info on that? thanks. - Original Message - From: Eric Bollengier e...@baculasystems.com To: users@ovirt.org Sent: Tuesday, March 4, 2014 12:29:09 PM Subject: [Users] How to get status of async operation via Java SDK Hello, From what I see in my tests, deleting a snapshot can take up to few minutes (my test platform is not really a heavy production system, but my VMs are powered off all the time, so I have hard time to know why the KVM Host is having a huge CPU consumption for this operation). So, I would like to know when the delete is actually done, and if the status is OK. I have pieces of information about a CorrelationId, I can read Events, but it's not really clear how to query the status of my operation, the Response object provides only a Type, and the documentation is oriented on creation. Documentation or some examples would be welcome. Thanks, Best Regards, Eric ___ 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] [ovirt test day 3] Documentation - man pages result
- Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Moti Asayag masa...@redhat.com, users@oVirt.org users@ovirt.org Cc: Doron Fediuck dfedi...@redhat.com Sent: Friday, March 7, 2014 9:15:50 AM Subject: Re: [ovirt test day 3] Documentation - man pages result Il 06/03/2014 23:32, Moti Asayag ha scritto: Hi, In the third ovirt test day I reviewed the manuals of a various ovirt tools and commands: Here are my findings (haven't reported any bugs for them): Please do, add keywords Documentation and ManPageChange for them Bugs were reported: Bug 1074301 - ovirt-shell has no man page Bug 1074300 - engine-manage-domains man page clarifications Bug 1074299 - engine-config man page clarifications Bug 1074302 - engine-upgrade-check has no man page Bug 1074303 - engine-backup has no man page The engine-backup and engine-upgrade-check has no man pages, however help is available by providing the --help argument: No manual entry for engine-backup No manual entry for engine-upgrade-check No manual entry for ovirt-shell engine-config man page: --- 1. engine-config ACTION [--cver=version] [-p | --properties=/path/to/alternate/property/fie] [-c | --config=/path/to/alter-nate/config/file] s/fie/file 2. version relevant configuration version to use should be: --cverrelevant configuration version to use 3. -g key, --get=key [--cversion=version] should be: -g key, --get=key [--cver=version] 4. The man pages misses an explanation how to set passwords using the --interactive argument which is described in the the output of engine-config --help engine-manage-domains man page: --- In general, there is a great complexity in explaining the usage of the command, too many combinations. 1. Examples: -action=add -domain=example.com --user=admin --provider=IPA --passwordFile=/tmp/.pwd Add a domain called example.com, using user admin with ldap server type IPA and read the password from /tmp/.pwd. The arguments --user, --provider and --passwordFile should be replaced with -user, -provider and -passwordFile respectively. 2. changePasswordMsg - doesn't appear in the man page (appears only via --help) Thanks, Moti -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Reimporting storage domains after reinstalling ovirt
On 09-03-14 14:11, Vered Volansky wrote: Hi Boudewijn, First of all, the wiki page you are referring to is a feature page that was never implemented. We are currently working on the same feature, this is the correct feature page: http://www.ovirt.org/Features/ImportStorageDomain . I will ask that the irrelevant page be removed to avoid any further confusion. Second, currently, the only way to import a domain is to create an export domain and import it. Can you get the old setup-up and create an export domain? If not, we'll try to help and work around this is issue, but this is going to be very complex, since this is not supported. Just to have a general understanding of your setup - your storage on the same machine as ovirt engine? I'm assuming you're using web-admin. What exactly are you doing there? We don't have the import option there as you mentioned, so I don't understand how you could import an SD that was not export. Adding the entry to /etc/exports is meaningless. Do you have the ovfs of the old VMs available? In the meantime checking for an easier solution than the above, will get back to you on that. Regards, Vered Dear Vered, Thank you very much for your reply; I didn't expect this (at first hand) simple action to be so hard/complex to perform. My machine is indeed a single machine containing both a node, webinterface and storage. The old setup has been reinstalled, so I can't get that one to work anymore. On the other hand I do still have a database dump from it. I'm using the webadmin indeed and if I go to storage there's a button saying import domain. In the dialogue that pops up after pressing that button it's mentioned that I should use a FQDN/IP notation which made me expect that it uses NFS ;-). Yes I do have ovf's, this is a directory listing from one of the storage domains: [root@leiden 1979444d-b79a-494c-8c1a-bcc132e31a04]# find . ./images ./images/6055a0a2-a6e9-4466-b0eb-3928c5c84d99 ./images/6055a0a2-a6e9-4466-b0eb-3928c5c84d99/9e5be41b-c512-4f22-9d7c-81090d62dc31 ./images/6055a0a2-a6e9-4466-b0eb-3928c5c84d99/9e5be41b-c512-4f22-9d7c-81090d62dc31.lease ./images/6055a0a2-a6e9-4466-b0eb-3928c5c84d99/9e5be41b-c512-4f22-9d7c-81090d62dc31.meta ./images/d72c41ff-2e34-474d-86be-3c11181b2128 ./images/d72c41ff-2e34-474d-86be-3c11181b2128/0dd635c7-ef77-4e0f-962c-90b66085ba93.lease ./images/d72c41ff-2e34-474d-86be-3c11181b2128/0dd635c7-ef77-4e0f-962c-90b66085ba93.meta ./images/d72c41ff-2e34-474d-86be-3c11181b2128/0dd635c7-ef77-4e0f-962c-90b66085ba93 ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6 ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/38eee7d5-9fd1-44b0-876c-b24e4bc0085b ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/988f90f6-a37d-4dfd-8477-70aa5d2db5b6.meta ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/38eee7d5-9fd1-44b0-876c-b24e4bc0085b.meta ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/988f90f6-a37d-4dfd-8477-70aa5d2db5b6 ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/38eee7d5-9fd1-44b0-876c-b24e4bc0085b.lease ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/988f90f6-a37d-4dfd-8477-70aa5d2db5b6.lease ./images/898c01ea-d7b5-4d59-8329-c9140f3e55c1 ./images/898c01ea-d7b5-4d59-8329-c9140f3e55c1/8b511fc2-4ec5-4c82-9faf-93da8490adc9.lease ./images/898c01ea-d7b5-4d59-8329-c9140f3e55c1/8b511fc2-4ec5-4c82-9faf-93da8490adc9.meta ./images/898c01ea-d7b5-4d59-8329-c9140f3e55c1/8b511fc2-4ec5-4c82-9faf-93da8490adc9 ./images/1f6b7b10-736c-4a6c-9743-a628f370ff2f ./images/1f6b7b10-736c-4a6c-9743-a628f370ff2f/8633fb9b-9c08-406b-925e-7d5955912165.lease ./images/1f6b7b10-736c-4a6c-9743-a628f370ff2f/8633fb9b-9c08-406b-925e-7d5955912165 ./images/1f6b7b10-736c-4a6c-9743-a628f370ff2f/8633fb9b-9c08-406b-925e-7d5955912165.meta ./images/c866dd6c-c7e5-419a-85e4-af49228be5a2 ./images/c866dd6c-c7e5-419a-85e4-af49228be5a2/5e56a396-8deb-4c04-9897-0e4f6582abcc.meta ./images/c866dd6c-c7e5-419a-85e4-af49228be5a2/5e56a396-8deb-4c04-9897-0e4f6582abcc.lease ./images/c866dd6c-c7e5-419a-85e4-af49228be5a2/5e56a396-8deb-4c04-9897-0e4f6582abcc ./images/a33a673d-751f-4287-a655-e84dfcfcd005 ./images/a33a673d-751f-4287-a655-e84dfcfcd005/2cd8d3dc-e92f-4be5-88fa-923076aba287.lease ./images/a33a673d-751f-4287-a655-e84dfcfcd005/2cd8d3dc-e92f-4be5-88fa-923076aba287 ./images/a33a673d-751f-4287-a655-e84dfcfcd005/2cd8d3dc-e92f-4be5-88fa-923076aba287.meta ./images/07b94c8d-8195-449b-b5e0-873bde6f85fd ./images/07b94c8d-8195-449b-b5e0-873bde6f85fd/efc46a9a-6fcd-4e48-a197-e6bdf1e655bf ./images/07b94c8d-8195-449b-b5e0-873bde6f85fd/efc46a9a-6fcd-4e48-a197-e6bdf1e655bf.lease ./images/07b94c8d-8195-449b-b5e0-873bde6f85fd/efc46a9a-6fcd-4e48-a197-e6bdf1e655bf.meta ./images/72dba8d6-4303-4db7-8a32-aafa0a3165a5 ./images/72dba8d6-4303-4db7-8a32-aafa0a3165a5/caecf666-302d-426c-8a32-65eda8d9e5df ./images/72dba8d6-4303-4db7-8a32-aafa0a3165a5/caecf666-302d-426c-8a32-65eda8d9e5df.lease ./images/72dba8d6-4303-4db7-8a32-aafa0a3165a5/caecf666-302d-426c-8a32-65eda8d9e5df.meta ./images/7fd446ce-bfb5-4706-9eb8-4133fcfbc00d
Re: [Users] Reimporting storage domains after reinstalling ovirt
On 03/09/2014 06:04 PM, Boudewijn Ector wrote: On 09-03-14 14:11, Vered Volansky wrote: Hi Boudewijn, First of all, the wiki page you are referring to is a feature page that was never implemented. We are currently working on the same feature, this is the correct feature page: http://www.ovirt.org/Features/ImportStorageDomain . I will ask that the irrelevant page be removed to avoid any further confusion. Second, currently, the only way to import a domain is to create an export domain and import it. Can you get the old setup-up and create an export domain? If not, we'll try to help and work around this is issue, but this is going to be very complex, since this is not supported. Just to have a general understanding of your setup - your storage on the same machine as ovirt engine? I'm assuming you're using web-admin. What exactly are you doing there? We don't have the import option there as you mentioned, so I don't understand how you could import an SD that was not export. Adding the entry to /etc/exports is meaningless. Do you have the ovfs of the old VMs available? In the meantime checking for an easier solution than the above, will get back to you on that. Regards, Vered Dear Vered, Thank you very much for your reply; I didn't expect this (at first hand) simple action to be so hard/complex to perform. hence the feature page you saw, to add this functionality (currently work in progress) My machine is indeed a single machine containing both a node, webinterface and storage. The old setup has been reinstalled, so I can't get that one to work anymore. On the other hand I do still have a database dump from it. I'm using the webadmin indeed and if I go to storage there's a button saying import domain. In the dialogue that pops up after pressing that button it's mentioned that I should use a FQDN/IP notation which made me expect that it uses NFS ;-). Yes I do have ovf's, this is a directory listing from one of the storage domains: [root@leiden 1979444d-b79a-494c-8c1a-bcc132e31a04]# find . ./images ./images/6055a0a2-a6e9-4466-b0eb-3928c5c84d99 ./images/6055a0a2-a6e9-4466-b0eb-3928c5c84d99/9e5be41b-c512-4f22-9d7c-81090d62dc31 ./images/6055a0a2-a6e9-4466-b0eb-3928c5c84d99/9e5be41b-c512-4f22-9d7c-81090d62dc31.lease ./images/6055a0a2-a6e9-4466-b0eb-3928c5c84d99/9e5be41b-c512-4f22-9d7c-81090d62dc31.meta ./images/d72c41ff-2e34-474d-86be-3c11181b2128 ./images/d72c41ff-2e34-474d-86be-3c11181b2128/0dd635c7-ef77-4e0f-962c-90b66085ba93.lease ./images/d72c41ff-2e34-474d-86be-3c11181b2128/0dd635c7-ef77-4e0f-962c-90b66085ba93.meta ./images/d72c41ff-2e34-474d-86be-3c11181b2128/0dd635c7-ef77-4e0f-962c-90b66085ba93 ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6 ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/38eee7d5-9fd1-44b0-876c-b24e4bc0085b ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/988f90f6-a37d-4dfd-8477-70aa5d2db5b6.meta ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/38eee7d5-9fd1-44b0-876c-b24e4bc0085b.meta ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/988f90f6-a37d-4dfd-8477-70aa5d2db5b6 ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/38eee7d5-9fd1-44b0-876c-b24e4bc0085b.lease ./images/df485d87-7dda-4cee-8fd0-5dc8b00d44c6/988f90f6-a37d-4dfd-8477-70aa5d2db5b6.lease ./images/898c01ea-d7b5-4d59-8329-c9140f3e55c1 ./images/898c01ea-d7b5-4d59-8329-c9140f3e55c1/8b511fc2-4ec5-4c82-9faf-93da8490adc9.lease ./images/898c01ea-d7b5-4d59-8329-c9140f3e55c1/8b511fc2-4ec5-4c82-9faf-93da8490adc9.meta ./images/898c01ea-d7b5-4d59-8329-c9140f3e55c1/8b511fc2-4ec5-4c82-9faf-93da8490adc9 ./images/1f6b7b10-736c-4a6c-9743-a628f370ff2f ./images/1f6b7b10-736c-4a6c-9743-a628f370ff2f/8633fb9b-9c08-406b-925e-7d5955912165.lease ./images/1f6b7b10-736c-4a6c-9743-a628f370ff2f/8633fb9b-9c08-406b-925e-7d5955912165 ./images/1f6b7b10-736c-4a6c-9743-a628f370ff2f/8633fb9b-9c08-406b-925e-7d5955912165.meta ./images/c866dd6c-c7e5-419a-85e4-af49228be5a2 ./images/c866dd6c-c7e5-419a-85e4-af49228be5a2/5e56a396-8deb-4c04-9897-0e4f6582abcc.meta ./images/c866dd6c-c7e5-419a-85e4-af49228be5a2/5e56a396-8deb-4c04-9897-0e4f6582abcc.lease ./images/c866dd6c-c7e5-419a-85e4-af49228be5a2/5e56a396-8deb-4c04-9897-0e4f6582abcc ./images/a33a673d-751f-4287-a655-e84dfcfcd005 ./images/a33a673d-751f-4287-a655-e84dfcfcd005/2cd8d3dc-e92f-4be5-88fa-923076aba287.lease ./images/a33a673d-751f-4287-a655-e84dfcfcd005/2cd8d3dc-e92f-4be5-88fa-923076aba287 ./images/a33a673d-751f-4287-a655-e84dfcfcd005/2cd8d3dc-e92f-4be5-88fa-923076aba287.meta ./images/07b94c8d-8195-449b-b5e0-873bde6f85fd ./images/07b94c8d-8195-449b-b5e0-873bde6f85fd/efc46a9a-6fcd-4e48-a197-e6bdf1e655bf ./images/07b94c8d-8195-449b-b5e0-873bde6f85fd/efc46a9a-6fcd-4e48-a197-e6bdf1e655bf.lease ./images/07b94c8d-8195-449b-b5e0-873bde6f85fd/efc46a9a-6fcd-4e48-a197-e6bdf1e655bf.meta ./images/72dba8d6-4303-4db7-8a32-aafa0a3165a5 ./images/72dba8d6-4303-4db7-8a32-aafa0a3165a5/caecf666-302d-426c-8a32-65eda8d9e5df ./images/72dba8d6-4303-4db7-8a32-aafa0a3165a5/caecf666-302d-426c-8a32-65eda8d9e5df.lease
Re: [Users] Reimporting storage domains after reinstalling ovirt
How should I go on recovering those VMs? change the domain into an export domain, attach it, and import the VMs from it (currently, you can only import an export domain) i think this thread has the relevant info: https://www.mail-archive.com/users@ovirt.org/msg04257.html Okay thank you very much for pointing that out. I now realise the difference between the regular and export shares. I just changed the metadata file (at /raid/ovirt-old/data/1979444d-b79a-494c-8c1a-bcc132e31a04/dom_md0) from: [root@leiden dom_md]# cat metadata.backup CLASS=Data DESCRIPTION=leiden-data IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=613 POOL_DESCRIPTION=Default POOL_DOMAINS=dafe25c2-1ce7-4979-9d8d-a35688da207a:Active,1979444d-b79a-494c-8c1a-bcc132e31a04:Active,d2676b04-e2ff-420f-8f29-36dafc2df47b:Active POOL_SPM_ID=1 POOL_SPM_LVER=0 POOL_UUID=5849b030-626e-47cb-ad90-3ce782d831b3 REMOTE_PATH=192.168.1.44:/raid/ovirt/data ROLE=Master SDUUID=1979444d-b79a-494c-8c1a-bcc132e31a04 TYPE=NFS VERSION=3 _SHA_CKSUM=cab6c41e19812714ba79c48fc98b7037032725e4 into: CLASS=Backup DESCRIPTION=export-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=613 POOL_DESCRIPTION=Default POOL_DOMAINS= POOL_SPM_ID=1 POOL_SPM_LVER=0 POOL_UUID= REMOTE_PATH=nfsserver:/raid/ovirt-old/data ROLE=Regular SDUUID=1979444d-b79a-494c-8c1a-bcc132e31a04 TYPE=NFS VERSION=3 (there's another storage doman which has to be converted too but that's not that relevant imo). Now I log in onto the webinterface, select storage domain - import domain : Domain function set to export/NFS export path: 192.168.1.44:/raid/ovirt-old/data/ (192.168.1.44 is the server's IP) Now this error pops up: Error while executing action: Cannot add Storage. Storage format V3 is not supported on the selected host version. I just had a look for this one and found this bug (in which you replied... such a small world :) ) : https://bugzilla.redhat.com/show_bug.cgi?id=1059604 But there's no obvious solution over there. Despite this the domains are available in the storage domain list but they're unattached so no use to me. Am I still missing something? Cheers, Boudewijn ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Reimporting storage domains after reinstalling ovirt
(there's another storage doman which has to be converted too but that's not that relevant imo). Now I log in onto the webinterface, select storage domain - import domain : Domain function set to export/NFS export path: 192.168.1.44:/raid/ovirt-old/data/ (192.168.1.44 is the server's IP) Now this error pops up: Error while executing action: Cannot add Storage. Storage format V3 is not supported on the selected host version. I just had a look for this one and found this bug (in which you replied... such a small world :) ) : https://bugzilla.redhat.com/show_bug.cgi?id=1059604 But there's no obvious solution over there. Despite this the domains are available in the storage domain list but they're unattached so no use to me. Am I still missing something? Cheers, Boudewijn ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Interesting: i just tried readding it again (maybe rereading the storage domain takes a lot of time) but despite it not showing up in the storage domain list, ovirt's webadmin tells met the repo has already been added: Error while executing action: Cannot add Storage Connection. Storage connection already exists. Strange. Cheers, Boudewijn ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] 3.4 iscsi multipath feature iface initiatorname
John, I and several guys here tested it either and it worked for us, however in your case we definitely have a problem. Can we schedule a meeting in the ovirt channel so we can manage continues conversation and examine all facts? Regards, Sergey - Original Message - From: John Taylor jtt77...@gmail.com To: users@ovirt.org Sent: Sunday, March 9, 2014 3:29:09 AM Subject: [Users] 3.4 iscsi multipath feature iface initiatorname Hi All, I'm testing the 3.4 iscsi multipath feature and I think I have a problem with the way it is creating iscsi ifaces. The background: I've got an existing production 3.3 system that is iscsi, and it is multipath in the sense that there are mulitple networks configured on the hosts that are used to connect to my iscsi storage (a fujtisu eternus) and the storage domain is configured with multiple targets for each lun. This has worked for me but it's not the explicit managed multipath that the new feature provides. So in my test 3.4 all-in-one, i've tried to follow the steps at http://www.ovirt.org/Feature/iSCSI-Multipath. I got the iscsi domain up, but when I added the iscsi bonds, my storage domain went offline. After digging through it, the reason is that the iscsi bond creates iscsi ifaces, and those ifaces have an initiatorname that is the name of the network, not the iscsi initiatorname defined in /etc/iscsi/initiatorname.iscsi this is the part of vdsm log that shows the iscsi iface creation Thread-275963::DEBUG::2014-03-06 16:58:15,743::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) '/usr/bin/sudo -n /sbin/iscsiadm -m iface' (cwd None) Thread-275963::DEBUG::2014-03-06 16:58:15,786::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) SUCCESS: err = ''; rc = 0 Thread-275963::DEBUG::2014-03-06 16:58:15,787::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) '/usr/bin/sudo -n /sbin/iscsiadm -m iface -I em1.218 --op=new' (cwd None) Thread-275963::DEBUG::2014-03-06 16:58:15,827::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) SUCCESS: err = ''; rc = 0 Thread-275963::DEBUG::2014-03-06 16:58:15,828::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) '/usr/bin/sudo -n /sbin/iscsiadm -m iface -I em1.218 -n iface.initiatorname -v em1.218 --op=update' (cwd None) Thread-275963::DEBUG::2014-03-06 16:58:15,875::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) SUCCESS: err = ''; rc = 0 Thread-275963::DEBUG::2014-03-06 16:58:15,876::iscsiadm::92::Storage.Misc.excCmd::(_runCmd) '/usr/bin/sudo -n /sbin/iscsiadm -m iface -I em1.218 -n iface.transport_name -v tcp --op=update' (cwd None) When those ifaces are used in the iscsiadm connections, I don't get the luns attached because they're not the correct initiatorname in the iscsi setup. I know Francesco wrote of success at http://lists.ovirt.org/pipermail/users/2014-January/020412.html Has anyone else seen this? Thanks, -John ___ 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