similar to: Announcing oVirt 0.99

This patch updates dbomatic, taskomatic and host-register to use the new C++ wrapped ruby QMF bindings. It also fixes a couple of bugs along the way including the 0 cpu bug for host-register. This is a compilation of work done by myself and Arjun Roy. Signed-off-by: Ian Main <imain at redhat.com> --- src/db-omatic/db_omatic.rb | 111 ++++++-------

The error is caused by the save! method updating an object that another thread (most likely in taskomatic) already updated. In the case of this race condition, we retry saving. However, a proper fix would involve fixing the locking. --- src/db-omatic/db_omatic.rb | 23 ++++++++++++++++++++--- 1 files changed, 20 insertions(+), 3 deletions(-) diff --git a/src/db-omatic/db_omatic.rb

Hi all, I've got some problems to make work oVirt. I've installed a Fedora 10 VM the lightest possible (nothing checked, even based) and installed after some packages (wget, sudo, acpid,...) and updated the system. By the way, acpid should be a dependency of ovirt-installer because the installation fails if it's not available. I've then installed ovirt (ovirt-server-installer

This patch fixes state changes in dbomatic so that there is no intermediate 'stopped' state after being unreachable or on startup of dbomatic etc. Also fixes a number of smaller bugs around host associations, state changes, etc. Signed-off-by: Ian Main <imain at redhat.com> --- src/db-omatic/db_omatic.rb | 85 +++++++++++++++++++++++++++++++------------- 1 files changed, 60

--- src/db-omatic/db_omatic.rb | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index 155ff5e..b5b7b81 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/db-omatic/db_omatic.rb @@ -270,10 +270,10 @@ class DbOmatic < Qpid::Qmf::Console end def object_props(broker, obj) - target =

This patch uses the qpid migration call which requires the latest libvirt-qpid and libvirt. I also add a bunch of debug logging here which is switchable but I've left it on for now so all users will have this in their logs. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/taskomatic.rb | 36 ++++++++++++++++++++++++++++-------- 1 files changed, 28 insertions(+), 8

The underlying issue has to do with optimistic locking for active record, and contention between db-omatic and task-omatic. That still needs to be fixed, especially since contention issues might get worse when the two daemons are made multithreaded. --- src/db-omatic/db_omatic.rb | 22 +++++++++++++++++++--- 1 files changed, 19 insertions(+), 3 deletions(-) diff --git

I just build the latest ovirt from git and have a problem with storage now. Creating the storage pool works but when i try to add a volume i get "Pending_setup" and then in tasks "wrong number of arguments (1 for 2)". taskomatic log shows : ERROR Sun May 31 10:30:37 +0200 2009 (28807) Task action processing failed: ArgumentError: wrong number of arguments (1 for 2) ERROR Sun

Also includes a couple minor model changes to support better error reporting. This method was added so that a client could submit multiple vms to the service layer in one call and get back appropriate messages showing any failures without those failures also causing the entire call to fail, or forcing the client to implement handling (begin/rescue blocks) of these errors to continue through the

Hi. I have successfully installed ovirt. Boot 2 nodex throught PXE boot, and added to pool. Whe i try to create NFS storage, they in state: pending setup. How to add NFS storage? taskomatic.log INFO Wed Sep 30 16:59:09 +0300 2009 (1991) starting task_refresh_pool INFO Wed Sep 30 16:59:09 +0300 2009 (1991) storage_find_suitable_host: host node3.ovirt.priv uuid 30303234-3144-3832-4638-3931FF

This patch changes taskomatic so it only sets the VM to shutdown if the undefine succeeds. Otherwise it's possible a shutdown event could not succeed, or take a while as it often does, giving confusing messages to the user. Basically we're just letting dbomatic handle it now. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/taskomatic.rb | 1 - 1 files

I have troubles with live migration since I upgraded libvirt on my nodes 1) I have to change 'Libvirt::Domain::MIGRATE_LIVE' to '1' in taskomatic error : Error: uninitialized constant Libvirt::Domain::MIGRATE_LIVE and why '1' : http://libvirt.org/html/libvirt-libvirt.html 2) the migration fails with this error : Task action processing failed: RuntimeError: Timed out

This patch increases the timeout value on taskomatic calls so that we get back the real libvirt errors instead of just having qmf timeout. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/task_storage.rb | 6 +++--- src/task-omatic/taskomatic.rb | 10 +++++----- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/task-omatic/task_storage.rb

Greetings Everyone, I have a question here regarding the ovirt node during boot. I have configured ovirt-server with all the procedures followed from wiki and finished each successfully. Also i tried booting one of the nodes with ovirt-node image through PXE boot. The machine which i booted got an dhcp IP (hostname) and was listed in the ovirt web gui. But there is a issue i have been seeing

This sets up ovirt-agent to start as a daemon along with dbomatic, taskomatic etc. While this is not ready for prime time I think it should be ok as you still require a valid, authenticated, connection to qpidd to access it. Signed-off-by: Ian Main <imain at redhat.com> --- installer/modules/ovirt/manifests/ovirt.pp | 6 +++ ovirt-server.spec.in | 5 ++

run on startup by default like the other ovirt services --- conf/ovirt-vnc-proxy | 49 ++++++++ installer/modules/ovirt/manifests/ovirt.pp | 1 + ovirt-server.spec.in | 5 + src/vnc-proxy/vnc-proxy.rb | 167 ++++++++++++++++++++++++++++ 4 files changed, 222 insertions(+), 0 deletions(-) create mode 100755 conf/ovirt-vnc-proxy

Hi all, We use for preproduction purpose the next branche of oVirt. We notice that a lot of bugs appears when the number of message in qpidd increase. It seems that qpidd is doing the job and that most of the issue are due to Qmf::Query . For example in db-omatic lines 265,296 When you restart db-omatic, if you have multiple node, you have mutiple threads launch (line 266) that hang on :

This fixes a bug where if db-omatic restarted, any running vm lost the association with the host it is running on in the db. --- src/db-omatic/db_omatic.rb | 11 +++++++++++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index b5b7b81..d2540e1 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/db-omatic/db_omatic.rb @@

--- src/task-omatic/task_storage.rb | 50 +++++++++++++++++++++++++++++++++++++++ src/task-omatic/utils.rb | 40 +++++++++++++++++++++++++++++++ 2 files changed, 90 insertions(+), 0 deletions(-) diff --git a/src/task-omatic/task_storage.rb b/src/task-omatic/task_storage.rb index 77363ac..97ae4fc 100644 --- a/src/task-omatic/task_storage.rb +++ b/src/task-omatic/task_storage.rb @@

Hi, I'm currently trying to merge db-omatic, taskomatic and host-register into a big EventMachine loop to solve some concurrency issues and be able to boot many vms faster. My problem is that each method call to libvirt blocks the loop for quite long (sometimes 0.7 seconds) and qmf aparently has a way to do it asynchronously but I have no idea how to do this with the qmf module for ruby. I