[Users] Failed to update ovirt-engine
Hi guys, The update failed because of the dependency on ovirt-engine-sdk, which is not available in http://www.ovirt.org/releases/beta/fedora/17/ How to fix it? Thanks! Mark. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] GNOME Boxes/oVirt integration
Hey, I've blogged yesterday about the recent work I've done to add oVirt support to GNOME Boxes ( https://live.gnome.org/Boxes/ ) using oVirt REST API: http://cfergeau.blogspot.fr/2012/07/outside-boxes.html « Outside Boxes oVirt Let's start this post with a quick presentation of oVirt (you'll understand why in a few paragraphs...). oVirt is a free project providing management, monitoring and provisioning of KVM virtual machines on multiple hosts. It comes with a web interface to create and manage virtual machines, hypervisor nodes, storage, ... and with a user portal for those who just want to connect to an already existing virtual machine. The way the user portal works is that you log into the portal from your browser, then you choose the virtual machine you want to connect to, and a browser plugin will take over and spawn an external binary (these days it's remote-viewer) oVirt also comes with an extensive REST API which lets you do programmatically the same thing as you can do from oVirt web UIs. Moreover, it has an extensive documentation. But what about GNOME? And now we are finally coming as to why I'm talking about all of this :) Lately, I've been hacking on Boxes, and since one of its goals is to view, access, and use shared connection / machine, I've decided it would be fun to make it support oVirt connections! This would make it easier for Boxes users to connect to oVirt virtual machines without having to go through their browser. librest already provides a good low-level GObject library to access REST services (though it was missing authentication support), so I used it to build a higher level library which wraps the oVirt REST accesses: libgovirt. This library uses GObject and gobject-introspection, which gives bindings to several other languages for free (including vala which is needed for Boxes). It also provides asynchronous methods for all its remote operations. The library is still young and only implements the few REST operations I needed (list oVirt virtual machines, get VM connection details, generate temporary VM display password, ...), but this is enough for Boxes needs ;) Once this library was in good shape, using it in Boxes was quite easy as the existing code was modular enough. All I had to do was to add a new URI type (ovirt://), and add a new Machine subclass to handle oVirt VMs, but most of the work is done by the libgovirt library. This work is not yet merged upstream but can be seen in my personal git repository. After some small cleanups and a libgovirt release, it should be in good shape for an upstream review and integration. As for libgovirt, there is a lot of API to bind (help welcome!), but binding this new 3.1 API will be mandatory to be able to connect to all oVirt-managed VMs. One possible way forward for libgovirt would be to leverage the python oVirt REST binding generator from ovirt-engine-sdk. And before ending this blog post, mandatory screenshots! » Cheers, Christophe pgpSveMvoBR8Q.pgp Description: PGP signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] VDSM and RHEL problem
- Original Message - From: Jonathan Cox jonathanheber...@gmail.com To: users@ovirt.org Sent: Monday, July 23, 2012 1:57:53 PM Subject: [Users] VDSM and RHEL problem Hello, I am running Ovirt 3.1 and everything was running well but then I decided to upgrade to a system with more memory for the engine and now the VDSM version dropped to 3.1 and the RHEL is complaining that there is no compatible pc. This wasnt a problem before and I tried to go back to the old system but now both of them are giving the same error. Anyone have any ideas what I should be looking to fix here? I am not sure if the 2 problems are related, I am running CentOS 6.3, Ovirt 3.1 and using the dreyou builds. Thanks -- Jonathan H Cox hi, did you follow http://wiki.ovirt.org/wiki/Engine_Node_Integration ? you need to make sure EmulatedMachine is set to the correct value according to your hosts, if you are using CentOS 6.3 i believe you need to set rhel6.3.0 in version 3.1 means run: psql -U postgres engine -c update vdc_options set option_value='rhel6.3.0' where option_name='EmulatedMachine' and version='3.1'; instead of the same line in the wiki (and restart jboss) ___ 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] release date Ovirt 3.1
- Original Message - Hi all, Any new about the Ovirt 3.1 release date? Will it be available this week...? We will have a release Go/No Go meeting in the start of the weekly oVirt sync (#ovirt irc channel), so I can't tell for sure. Can't wait! Winfried ___ 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] Wondering about updating ovirt from 3.0 to 3.1
- Original Message - On 07/12/2012 06:08 PM, Robert Middleswarth wrote: On 07/12/2012 03:01 PM, Dominic Kaiser wrote: So does Fedora 16 have an Ovirt 3.1 repo? It seems best way to do this correct me if I am wrong: No. There are no Fedora 16 Repo's 1. Uninstall 3.0 2. engine-cleanup do not drop database 3. Reinstall Good to go right? Will this mess with vm's already running etc. Pretty certain this will break things badly. The un-test but the way that should work is. Uninstall oVirt 3.0 do not engine-clean Upgrade from Fedora 16 to Fedora 17. Add the beta repo's yum clean all Yum install ovirt-engine Run enginue-upgrade and follow it instructions I'm afraid this won't work, we changed so many things in the packaging/setup between 3.0 and 3.1 Has anyone else tested this? I just tried it on a test rig of F16 running 3.0, upgrading to 3.1 beta on F17. All the steps completed fine, except that I had to remove ovirt-engine-jbossas, which conflicted with the new, from Fedora, jboss-as, before installing ovirt-engine 3.1. After engine-upgrade completed, I wasn't able to access the engine. Jboss-as was stopped, as was httpd. Starting them up didn't make the engine accessible, though. I just got the default fedora pages for JBoss and for Apache. On my own oVirt setup, I moved from 3.0 to 3.1 by moving my VMs and templates to my export domain, detaching my export and iso domains, and installing 3.1 from scratch, before importing my iso and export domains and ferrying my VMs and templates over to my new data domain. What's the most sane upgrade advice we can offer to oVirt 3.0 users? Jason the sane upgrade path (nothing is sane in Fedora 16 to Fedora 17 upgrade): 1. run engine-cleanup, do not drop DB 2. remove all ovirt-engine rpms (including the JBoss one) - please not that this will remove the PKI, so you'll have to re-install your hosts 3. Do the fedora upgrade 4. install ovirt-engine rpms 5. run engine-setup - Give same passwords to the DB/admin user in this case, engine-setup should upgrade the db, and not install it. we didn't tried this approach yet, so I'll appreciate any input. Since I was stuck at the DMV all day I haven't had a change to test these instructions at all before doing these steps I would do a full backup of the DB and a snapshot of the system. If you can clone the system and do these steps on a clone even better. Thanks Robert dk On Thu, Jul 12, 2012 at 11:26 AM, Robert Middleswarth rob...@middleswarth.net mailto:rob...@middleswarth.net wrote: On 07/12/2012 11:23 AM, Dominic Kaiser wrote: What is the proper process for this in ovirt? Or has someone done it already? Testing is just getting started. We have an idea of the steps but no one has actually done them to see if the upgrade works or not. Thanks Robert Thanks, -- Dominic Kaiser Greater Boston Vineyard Director of Operations cell: 617-230-1412 tel:617-230-1412 fax: 617-252-0238 tel:617-252-0238 email: domi...@bostonvineyard.org mailto:domi...@bostonvineyard.org ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dominic Kaiser Greater Boston Vineyard Director of Operations cell: 617-230-1412 fax: 617-252-0238 email: domi...@bostonvineyard.org mailto:domi...@bostonvineyard.org ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Jason Brooks Media Communications Open Source and Standards @ Red Hat identi.ca/jasonbrooks twitter.com/jasonbrooks ___ 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] Wondering about updating ovirt from 3.0 to 3.1
- Original Message - From: Ofer Schreiber oschr...@redhat.com To: Jason Brooks jbro...@redhat.com Cc: users@ovirt.org Sent: Tuesday, July 24, 2012 7:13:32 AM Subject: Re: [Users] Wondering about updating ovirt from 3.0 to 3.1 - Original Message - On 07/12/2012 06:08 PM, Robert Middleswarth wrote: On 07/12/2012 03:01 PM, Dominic Kaiser wrote: So does Fedora 16 have an Ovirt 3.1 repo? It seems best way to do this correct me if I am wrong: No. There are no Fedora 16 Repo's 1. Uninstall 3.0 2. engine-cleanup do not drop database 3. Reinstall Good to go right? Will this mess with vm's already running etc. Pretty certain this will break things badly. The un-test but the way that should work is. Uninstall oVirt 3.0 do not engine-clean Upgrade from Fedora 16 to Fedora 17. Add the beta repo's yum clean all Yum install ovirt-engine Run enginue-upgrade and follow it instructions I'm afraid this won't work, we changed so many things in the packaging/setup between 3.0 and 3.1 Has anyone else tested this? I just tried it on a test rig of F16 running 3.0, upgrading to 3.1 beta on F17. All the steps completed fine, except that I had to remove ovirt-engine-jbossas, which conflicted with the new, from Fedora, jboss-as, before installing ovirt-engine 3.1. After engine-upgrade completed, I wasn't able to access the engine. Jboss-as was stopped, as was httpd. Starting them up didn't make the engine accessible, though. I just got the default fedora pages for JBoss and for Apache. On my own oVirt setup, I moved from 3.0 to 3.1 by moving my VMs and templates to my export domain, detaching my export and iso domains, and installing 3.1 from scratch, before importing my iso and export domains and ferrying my VMs and templates over to my new data domain. What's the most sane upgrade advice we can offer to oVirt 3.0 users? Jason the sane upgrade path (nothing is sane in Fedora 16 to Fedora 17 upgrade): 1. run engine-cleanup, do not drop DB 2. remove all ovirt-engine rpms (including the JBoss one) - please not that this will remove the PKI, so you'll have to re-install your hosts 3. Do the fedora upgrade 4. install ovirt-engine rpms 5. run engine-setup - Give same passwords to the DB/admin user in this case, engine-setup should upgrade the db, and not install it. we didn't tried this approach yet, so I'll appreciate any input. Can someone please try this out and verify it works? I'd like to include this process in the release notes. Thanks, Steve ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Update of oVirt 3.1
Good evening, I had installed the 3.1 beta version. After an update of Fedora 17, the portal does not show any links. I reckon that ovirt-engine version has been upgraded to 3.1.0-1.fc17. Have I lost all the information in the database? Is there a way to bring back the datacenters and the nodes info? Regards, Jose Garcia ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Wondering about updating ovirt from 3.0 to 3.1
What's the most sane upgrade advice we can offer to oVirt 3.0 users? Jason the sane upgrade path (nothing is sane in Fedora 16 to Fedora 17 upgrade): 1. run engine-cleanup, do not drop DB 2. remove all ovirt-engine rpms (including the JBoss one) - please not that this will remove the PKI, so you'll have to re-install your hosts 3. Do the fedora upgrade 4. install ovirt-engine rpms 5. run engine-setup - Give same passwords to the DB/admin user in this case, engine-setup should upgrade the db, and not install it. we didn't tried this approach yet, so I'll appreciate any input. Can someone please try this out and verify it works? I'd like to include this process in the release notes. I've been testing this path today. I get all the way to step 5, running engine-setup, and the script fails out after asking for my existing db password. The script asks for my password, over and over (I tried entering it like 25 times) and keeps on asking until I hit enter with a blank password a couple of times, at which point it fails out. Jason Thanks, Steve ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Failed to update ovirt-engine
On 07/24/2012 05:23 PM, Ofer Schreiber wrote: - Original Message - Hi guys, The update failed because of the dependency on ovirt-engine-sdk, which is not available in http://www.ovirt.org/releases/beta/fedora/17/ How to fix it? Repo was fixed, thanks for the report. (and sorry for the inconvenience, we had some issues regenerating the repo last week) Thanks! Mark. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thanks for the quick fix! ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Wondering about updating ovirt from 3.0 to 3.1
- Original Message - From: Jason Brooks jbro...@redhat.com To: Steve Gordon sgor...@redhat.com Cc: Ofer Schreiber oschr...@redhat.com, users@ovirt.org Sent: Tuesday, July 24, 2012 6:50:24 PM Subject: Re: [Users] Wondering about updating ovirt from 3.0 to 3.1 What's the most sane upgrade advice we can offer to oVirt 3.0 users? Jason the sane upgrade path (nothing is sane in Fedora 16 to Fedora 17 upgrade): 1. run engine-cleanup, do not drop DB 2. remove all ovirt-engine rpms (including the JBoss one) - please not that this will remove the PKI, so you'll have to re-install your hosts 3. Do the fedora upgrade 4. install ovirt-engine rpms 5. run engine-setup - Give same passwords to the DB/admin user in this case, engine-setup should upgrade the db, and not install it. we didn't tried this approach yet, so I'll appreciate any input. Can someone please try this out and verify it works? I'd like to include this process in the release notes. I've been testing this path today. I get all the way to step 5, running engine-setup, and the script fails out after asking for my existing db password. The script asks for my password, over and over (I tried entering it like 25 times) and keeps on asking until I hit enter with a blank password a couple of times, at which point it fails out. Jason Hi Jason, Any chance you could upload the engine-setup log somewhere for us to take a look at? Thanks, Steve ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Wondering about updating ovirt from 3.0 to 3.1
- Original Message - From: Steve Gordon sgor...@redhat.com To: Jason Brooks jbro...@redhat.com Cc: Ofer Schreiber oschr...@redhat.com, users@ovirt.org Sent: Tuesday, July 24, 2012 8:01:05 PM Subject: Re: [Users] Wondering about updating ovirt from 3.0 to 3.1 - Original Message - From: Jason Brooks jbro...@redhat.com To: Steve Gordon sgor...@redhat.com Cc: Ofer Schreiber oschr...@redhat.com, users@ovirt.org Sent: Tuesday, July 24, 2012 6:50:24 PM Subject: Re: [Users] Wondering about updating ovirt from 3.0 to 3.1 What's the most sane upgrade advice we can offer to oVirt 3.0 users? Jason the sane upgrade path (nothing is sane in Fedora 16 to Fedora 17 upgrade): 1. run engine-cleanup, do not drop DB 2. remove all ovirt-engine rpms (including the JBoss one) - please not that this will remove the PKI, so you'll have to re-install your hosts 3. Do the fedora upgrade 4. install ovirt-engine rpms 5. run engine-setup - Give same passwords to the DB/admin user in this case, engine-setup should upgrade the db, and not install it. we didn't tried this approach yet, so I'll appreciate any input. Can someone please try this out and verify it works? I'd like to include this process in the release notes. I've been testing this path today. I get all the way to step 5, running engine-setup, and the script fails out after asking for my existing db password. The script asks for my password, over and over (I tried entering it like 25 times) and keeps on asking until I hit enter with a blank password a couple of times, at which point it fails out. Jason Hi Jason, Any chance you could upload the engine-setup log somewhere for us to take a look at? Here it is: http://fpaste.org/m3rt/ Jason Thanks, Steve ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
