similar to: [PATCH server] Make volume finding more robust.

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

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 ++++++-------

This patch teaches taskomatic to use the volume 'key' instead of the path from libvirt to key the volume off of in the database. This fixes the duplicate iscsi volume bug we were seeing. The issue was that libvirt changed the way they name storage volumes and included a local ID that changed each time it was attached. Note that the first run with this new patch will cause duplicate

Somehow I missed this.. this file is no longer in use by taskomatic. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/utils.rb | 221 ---------------------------------------------- 1 files changed, 0 insertions(+), 221 deletions(-) delete mode 100644 src/task-omatic/utils.rb diff --git a/src/task-omatic/utils.rb b/src/task-omatic/utils.rb deleted file mode 100644 index

Since Ruby::Qmf moves, the .key() method does not work anymore. It forces to use a .get_attr('key') in order to get the good value. Signed-off-by: Loiseleur Michel <mloiseleur at linagora.com> --- src/task-omatic/taskomatic.rb | 15 +++++++-------- 1 files changed, 7 insertions(+), 8 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index

This patch adds more debug calling in storage related tasks. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/task_storage.rb | 29 ++++++++++++++++++----------- src/task-omatic/taskomatic.rb | 18 +++++++++--------- 2 files changed, 27 insertions(+), 20 deletions(-) diff --git a/src/task-omatic/task_storage.rb b/src/task-omatic/task_storage.rb index

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

It seems people were getting confused by the message that taskomatic was disconnected and not logging a reconnect message. This patch makes it log on reconnect as well. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/taskomatic.rb | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb

This patch just checks the broker to see if it's connected before attempting to implement tasks. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/taskomatic.rb | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index 5393c29..71432d2 100755 --- a/src/task-omatic/taskomatic.rb +++

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

From: Simon Courtois <scourtois at linagora.com> Signed-off-by: Simon Courtois <scourtois at linagora.com> --- src/app/controllers/vm_controller.rb | 19 ++++++++++++++++- src/app/views/vm/_form.rhtml | 25 ++++++++++++++++++++--- src/db/migrate/044_add_virtio_to_vm_and_nic.rb | 11 ++++++++++ src/public/stylesheets/components.css | 5

Previously, a pxe-booted vm would always boot to HD at next startup. Signed-off-by: Nicolas Ochem <nicolas.ochem at alcatel-lucent.com> --- src/app/controllers/vm_controller.rb | 1 + src/app/models/vm.rb | 15 +++++++++++---- src/app/views/vm/_form.rhtml | 2 +- src/task-omatic/taskomatic.rb | 13 +++++++++++-- 4 files changed, 24 insertions(+), 7

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 ++

Hi, Does somebody know what is the purpose of this line in taskomatic.rb : set_vm_vnc_port(db_vm, result.description) unless result.status != 0 We removed it to avoid 2 errors in taskomatic.log when a vm is launched : ERROR Mon Aug 30 15:23:00 +0000 2010 (26416) Task action processing failed: ActiveRecord::RecordInvalid: Validation failed: Vnc port must be greater than or equal to 0 ERROR

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

Hi, is there a good reason why taskomatic check the number of real cores in the find_capable_host ? It prevents to use the full capacity of multithreading Signed-off-by: Arthur Clement <aclement at linagora.com> --- src/task-omatic/taskomatic.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index

--- src/task-omatic/taskomatic.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index 7de725d..0314e6a 100755 --- a/src/task-omatic/taskomatic.rb +++ b/src/task-omatic/taskomatic.rb @@ -548,7 +548,7 @@ class TaskOmatic dest_uri = "qemu+tcp://" + dest_node.hostname + "/system"

Signed-off-by: Simon Courtois <scourtois at linagora.com> --- src/task-omatic/taskomatic.rb | 5 ++--- 1 files changed, 2 insertions(+), 3 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index 471ec88..1dfd74f 100755 --- a/src/task-omatic/taskomatic.rb +++ b/src/task-omatic/taskomatic.rb @@ -355,11 +355,10 @@ class TaskOmatic end end

I've been playing with ovirt built from source. When I try to start my first VM, I get this error in taskomatic.log: INFO Wed Aug 26 14:33:28 -0600 2009 (12750) starting task_start_vm INFO Wed Aug 26 14:33:29 -0600 2009 (12750) VM will be started on node node94.ovirt.priv DEBUG Wed Aug 26 14:33:29 -0600 2009 (12750) Connecting volumes: DEBUG Wed Aug 26 14:33:29 -0600 2009 (12750) XML Domain

Live migration is an operation which can takes times, like 2 or 3 minutes for heavy vms. Fixing this timeout work around another bug of db-o-matic: the infinite loop where node A has a defined & stopped vm X and node B has a defined & running vm X. I encountered this bug because the live migration has hit the timeout limit. Signed-off-by: Loiseleur Michel <mloiseleur at