similar to: Build fails due to missing ovirt-node-recipe.ks

----- "Nicolas Ochem" <nicolas.ochem at alcatel-lucent.com> wrote: > > However for this to work you need to add runtime_mode=ovirt in > pxelinux.cfg/default in the kernel boot options. > Fantastic! Thanks Nicolas, that's done the trick. The node now boots and sets up it's interfaces. The host now appears in the management server user interface and

> - ace -d install ovirt has one error : package ovirt-node-image-pxe > not > found I get an error when FreeIPA is set up. Then a whole heap of notices and warning about a missing dependancy (presumably FreeIPA) debug: //freeipa::bundled/Single_exec[ipa_server_install]: Executing '/usr/sbin/ipa-server-install -r ovirt.priv -p 'supersecretpw' -P 'supersecretpw' -a

----- "Justin Clacherty" <justin at redfish-group.com> wrote: > > I ran ipa-server-install from the command line and the error it's > getting is this: > > Traceback (most recent call last): > File "/usr/sbin/ipa-server-install", line 41, in <module> > import ipaserver.krbinstance > File

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

cc-to ovirt-devel skipping cobbler seems to be the best solution since ovirt-node-image-pxe rpm does not exist anymore. However for this to work you need to add runtime_mode=ovirt in pxelinux.cfg/default in the kernel boot options. In the node, it's useful to check /var/log/ovirt.log for correct operation. > The monkey patch was already there. The /etc/hosts entry for

Hi everyone, It's been awhile since there have been any updates to the oVirt project but that's going to be changing shortly. We've re-launched the http://ovirt.org site and made a number of updates to the wiki. Additional updates will be coming over the coming days and weeks. As for the projects themselves, we're changing the focus a little for the overall oVirt project.

> I built and installed everything from next repo in fedora 13 minimal > following the build instructions in the website. Cool, now that at least one person has managed it I'll give it another go. > - the instructions to build the server rpm are missing from the > website Did you just do what I had outlined in my last email? ie. - cd to server directory - ./autogen.sh -

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

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

After running for a while the node becomes "unavailable" in the server UI. All VMs running on that node also become unavailable. The node is still running fine as are all the VMs, they're just no longer manageable. I looked on the node and everything appeared to be running fine. Looked on the server and ovirt-taskomatic was stopped (this seems to happen quite a bit).

The purpose of this patch is to add the matahari qmf agent package (http://git.et.redhat.com/?p=matahari.git;a=summary) to the node image. Matahari is a qmf agent that publishes hardware information to an amqp broker, replacing functionality from ovirt-identify-node. However, since the capability is not ovirt specific, the agent is maintained as a separate project (see link above). Dependencies

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

Purpose : fail iso build on encountering error in arbitrary code '$CODE' 1. export 'WDIR' , for 'CODE' to pick-up location to create 'fail' file to indicate failure, note that it may not always be possible to return some error code on failure in 'CODE' 2. 'set' commands enclosing 'CODE' will not be required 3. 'CODE' 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

Due to a typo, the defaulting of OVIRT_CACHE_DIR in the recipe Makefile.am was broken. Signed-off-by: Mike Burns <mburns at redhat.com> --- recipe/Makefile.am | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/recipe/Makefile.am b/recipe/Makefile.am index fb34437..d09905a 100644 --- a/recipe/Makefile.am +++ b/recipe/Makefile.am @@ -27,7 +27,7 @@ ARCH =

The previous patch, for whatever reason, fails to apply on top of tip. This patch is reimplemented and, hopefully, fixed.

Hi, Ovirt, I was trying to download and see Ovirt ruby and rail server code, but I see all python code under ovirtserver folder. Where can I see Ovirt management server's web ui codes?

Ovirt-post wasn't dependent on libvirtd being started. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-post | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/scripts/ovirt-post b/scripts/ovirt-post index 951d108..326c0b8 100755 --- a/scripts/ovirt-post +++ b/scripts/ovirt-post @@ -4,7 +4,7 @@ # ### BEGIN INIT INFO # Provides: ovirt-post -#

Hi Ovirt node image build problem? Node image build my system OS Fedora core 14. I am have a question about installation process of oVirt project. Install DOC : https://fedorahosted.org/ovirt/wiki/Build But node-image build error? [root at Ovirt-T node]# ./autobuild.sh Running oVirt Node Autobuild test -f Makefile && make -k distclean || :