similar to: [PATCH] Set up ovirt-agent so it starts as a daemon

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

Updates the installer to handle the scenario in which the guest and admin networks are the same by using an alternative httpd conf. Verified to work (eg oVirt managed vms are bootable) on the oVirt appliance so far. --- conf/ovirt-server.conf | 88 -------------------- installer/bin/ovirt-installer | 11 +--

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

Nodes will use rsyslog to forward their logs to the server in /var/log/remote. --- installer/modules/ovirt/files/rsyslog.conf | 65 ++++++++++++++++++++ installer/modules/ovirt/manifests/ovirt.pp | 26 ++++++++ .../modules/ovirt/templates/ovirt-dns.conf.erb | 1 + ovirt-server.spec.in | 3 + scripts/ovirt-rsyslog-kerbsetup

FIXME this patch isn't complete, still need to figure out the ldap command to wait for that service, something along the lines of: ldapsearch -b dc=priv,dc=ovirt,dc=org -x (but how will we parse the base from the installer? also this cmd fails, how to fix?) --- installer/modules/ovirt/manifests/ovirt.pp | 8 +++++- installer/modules/ovirt/manifests/postgres.pp | 13 ++++++---

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

From: Scott Seago <sseago at redhat.com> This adds some of the network API stuff to ovirt-agent. It's still not complete but what is there is functional. Signed-off-by: Ian Main <imain at redhat.com> --- src/ovirt-agent/lib/ovirt.rb | 3 + .../ovirt/controllers/hardwarepool_controller.rb | 2 +- .../lib/ovirt/controllers/network_controller.rb |

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

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

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

rhbz#723115 Signed-off-by: Mike Burns <mburns at redhat.com> --- ovirt-node.spec.in | 4 ++++ scripts/ovirt-early | 6 +++++- 2 files changed, 9 insertions(+), 1 deletions(-) diff --git a/ovirt-node.spec.in b/ovirt-node.spec.in index 2d8a4bf..8321ba7 100644 --- a/ovirt-node.spec.in +++ b/ovirt-node.spec.in @@ -180,6 +180,9 @@ echo "# File where default configuration is

I'm looking for feedback on this first patch. The node has been pushed towards a more generic boot process. With this patch the node can now boot up and execute a few specifically-named scripts that reside in /etc/node.d/ at key points during the startup. After this goes upstream, the next step will be to define in more detail the remote interfaces for the "managed" runtime

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

This patch supercedes the previous one by moving the functionality for relocating files into the make system.

--- 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 just recoginze that dovecot contains an rpm spec file. unfortunately it's not too useful since an rpm -ta dovecot-.x.y.tar.gz can't be used since just the dovecot.spec.in is in the tarbar and not the actual spec file (which is in this from not useful in the above form). anyway here is my patch to the spec.in. -- Levente "Si vis pacem