similar to: Node unavailable after ovirt-server reboot

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

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

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

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

Hi all, I looked at patching oVirt Server to work with the latest Matahari schema, from Matahari's 'next' branch, version 0.4.0. ovirt-server depends on matahari version 0.0.5, which is currently latest in Fedora, and it is used during Node registration, to enumerate hardware information. Usage extracted from src/host-browser/host-register.rb is as follows: host_list =

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

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:

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

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

This class has been replaced by the ProcessorsAgent. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- src/Makefile.am | 4 - src/cpu.cpp | 216 ------------------------------------------------------- src/cpu.h | 111 ---------------------------- src/host.cpp | 24 ------ src/host.h | 3 - src/schema.xml | 16 ---- 6 files changed, 0 insertions(+),

Refactoring the previous patch ended up creating two deltas. This patch pushes them both together into a single commit.

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(-)

This patch includes one small change: the Processors::get_load_average() method is now const since it does not change the object's state.

After some feedback from Slow, mainly about the load_average API being a method rather than an ongoing statistic. So I've converted the code over to instead update the load average statistic on a regular basis.

In looking at the code I realized that the last of the HAL depenencies were removed with this patch. So, I'm pushing an updated patch that contains none of the HAL code in it.