similar to: QMF API for Ovirt

This is the new ovirt agent that implements the QMF API. This is just its humble beginnings. The goal was to implement the create VM method on VMs but it turns out we need to specify the VM pool in order to do that. This is currently hardcoded to '5' and works locally but would likely not work elsewhere. What does work well is listing/querying of existing VMs. There is still lots of

Just a quick script modeled after the libvirt-qpid example that dumps all connected ovirt-node hardware info to standard out, for debug purposes. --- src/qmf-matahari.example.rb | 50 +++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 50 insertions(+), 0 deletions(-) create mode 100644 src/qmf-matahari.example.rb diff --git a/src/qmf-matahari.example.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

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

The purpose of this patch is to add support for the matahari qmf agent package (http://git.et.redhat.com/?p=matahari.git;a=summary) to the node. The following actions are taken: 1. Deprecate ovirt-identify-node and ovirt-listen-awake by removing them from the autotools scripts, the rpm spec and the node startup scripts. 2. Remove ovirt-listen-awake and ovirt-identify-node completely. 3. Add

The original bug report is filed here: http://issues.apache.org/jira/browse/QPID-1973 The svn revision 975209 and onwards for qpid contains the fix. --- src/host-browser/host-register.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/host-browser/host-register.rb b/src/host-browser/host-register.rb index 57c11b7..06d8553 100755 ---

This patch renames qmf-libvirt-example to libvirt-list and makes it not repeat. Useful for debugging. File mode is also now 755. Signed-off-by: Ian Main <imain at redhat.com> --- src/libvirt-list.rb | 65 +++++++++++++++++++++++++++++++++++++++ src/qmf-libvirt-example.rb | 72 -------------------------------------------- 2 files changed, 65 insertions(+), 72 deletions(-)

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 :

Announcing oVirt 0.99 ===================== We are pleased to announce the release of oVirt 0.99, a significant step forward in stability and feature set for oVirt project users. Some highlights from the change log: * Improved installer, oVirt Server will now install with an existing FreeIPA setup present rather than insisting on installing FreeIPA from scratch * Anyterm console support --

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 is the first step towards separating the APIs from the means by which they are carried between the remote and local system. Added a few new classes and types: * HostTransport - defines a type for talking to the Host * Host - the public contract for the host APIs * HostAgent - the QMF transport layer Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- .gitignore

This patch teaches ovirt-test to use the usual DNS SRV records to connect to qpidd so we don't have to enter the server etc. on the command line. Signed-off-by: Ian Main <imain at redhat.com> --- src/ovirt-agent/ovirt-test.rb | 8 ++------ 1 files changed, 2 insertions(+), 6 deletions(-) diff --git a/src/ovirt-agent/ovirt-test.rb b/src/ovirt-agent/ovirt-test.rb index

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

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 patchset removes ovirt-identify-node and ovirt-listen awake. It adds startup script support for the matahari qmf agent, which takes over the responsibility for communicating node hardware capabilities to the ovirt-server. On the server side, host-browser has had its node identification functionality replaced by a new script, host-register, which is what interfaces with the matahari qmf agent

The Processors agent reports details regarding the processing power for the managed node. Defined the agent within schema.xml. Wrote the wrapper code to create and populate an instance of the agent. The properties for the Processors agent have also been trimmed back to what is readily available via HAL. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- src/Makefile.am | 26

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

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

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

Hello I found on ovirt.org instruction for set unavailable(enable) to available(enable) i run "ruby /usr/share/ovirt-server/qmf-libvirt-example.rb" and get Error caching credentials; attempting to continue... Connecting to amqp://main.forex-24h.com:5672.. /usr/lib/ruby/site_ruby/1.8/qpid/delegates.rb:209:in `connection_start'/usr/lib/ruby/site_ruby/1.8/qpid/delegates.rb:209: