similar to: Condor Cloud + oVirt Node

Since create-ovirt-network script has been deprecated (was part of ovirt-appliance repo) we can't default to bridge on the host of ovirtbr0 for doing fake node testing. So default to network:default and allow manual override to something like bridge:breth0 Signed-off-by: Perry Myers <pmyers at redhat.com> --- create-ovirt-iso-nodes | 11 +++++++---- 1 files changed, 7 insertions(+),

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.

Hello dear R-help group (and David Smith from REvolution), I would like to perform parallel computing using R with Condor (hopefully using foreach or other recommended solutions, if available) for some "Embarrassingly parallel" problem. I will start by listing what I found so far, and then go on asking for help. So far I found the a manual by Xianhong Xie from Rnews_2005-2 (see page

Hi, I was wondering if anyone has successfully linked R against the Condor libraries so that R can be run as a Condor job in the "standard" (not "vanilla") universe. The advantage of this would be that due to checkpointing, jobs can be suspended and transferred to another node. There is a good overview by Xianhong Xie here:

Dear Experts, Could someone recommend some "quick and dirty" HOWTO on condor based cluster? A did a bunch of cluster setups, I always used PBS (or torque lately). But my professor wants his to be Condor. I started reading Condor documentation, and it is vast. And quick route, like: architecture chart, and parameters I need to configure on master/submit, and compute nodes - somehow

Hello, I would be extremely grateful if anyone is able to provide any (rather obscure) advice on using R with Condor. I think I'm following Xianhong Xie's instructions (R News 5(2) 13-15) correctly, but my job just stays held in the queue (for days / months). I've checked condor_status to make sure there are plenty of machines available, but can't see any way to attack the

Hello all, Recently I started playing with running R scripts on the Condor system in my institute. (For more on this, have a look at: Running Long R Jobs with Condor DAG by Xianhong Xie link: http://cran.r-project.org/doc/Rnews/Rnews_2005-2.pdf ) Might someone advice me about the following question: How should I handle the RNG (random number generation) in the running of parallel instances of R

rhbz#:51422 --- ovirt-node.spec.in | 149 +++++++++------------------------------------------ 1 files changed, 27 insertions(+), 122 deletions(-) diff --git a/ovirt-node.spec.in b/ovirt-node.spec.in index 3138011..b4e660d 100644 --- a/ovirt-node.spec.in +++ b/ovirt-node.spec.in @@ -43,76 +43,23 @@ Requires: nc Requires: grub Requires: /usr/sbin/crond Requires: anyterm

Added a new subdirectory called "isobuilder" to the project. Created a new Makefile that only allows for creating the livecd version of the oVirt node. Adjusted the build environment to work with the kickstart files that are found in the repo and not ones installed via any previous RPM. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- configure.ac | 1 +

modified ovirt-node-image for inclusion in Fedora Removes ovirt-node-image-pxe sub package adds get-ovirt-node-image script adds generate-ovirt-node-pxe-tree script (replaces subpackage) moved all the scripts/tools into tools subdir adds new rpm, ovirt-node-recipe includes tools, manifests, and ks file/recipe Process for building upstream ovirt node packages.... 1. Build ovir-node.rpm in koji

From: root <root at linagora-ovirt.netaktiv.com> --- ovirt-node-image.ks | 16 ++++++++++++++++ 1 files changed, 16 insertions(+), 0 deletions(-) diff --git a/ovirt-node-image.ks b/ovirt-node-image.ks index 802b6a5..9a7d617 100644 --- a/ovirt-node-image.ks +++ b/ovirt-node-image.ks @@ -55,6 +55,22 @@ if [ -f "ovirt-authorized_keys" ]; then chmod 644

From: root <root at chappy.(none)> --- ovirt-node-image.ks | 16 ++++++++++++++++ 1 files changed, 16 insertions(+), 0 deletions(-) diff --git a/ovirt-node-image.ks b/ovirt-node-image.ks index 802b6a5..d698497 100644 --- a/ovirt-node-image.ks +++ b/ovirt-node-image.ks @@ -55,6 +55,22 @@ if [ -f "ovirt-authorized_keys" ]; then chmod 644

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

Old edit-livecd just kept adding to the ext2 fs image which meant it never decreased in size even if files were removed. New functionality does multiple passes of ext2fs creation. First pass creates a new ext2fs from the image file inside the squashfs. This first pass is to allow the user to optionally increase the filesystem size. If the -s parameter is omitted the existing size is used and

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]# ./autogen.sh I am going to run ./configure with no arguments - if you wish to pass any to it, please specify them on the

This is the second generation of the edit-livecd tool that replaces our original bash script with a python version and aims to reuse as much as the livecd-creator libraries as possible. The main reason for the new creator class is to avoid the need for a kisckstart file in order to edit an existing livecd image. edit-livecd is useful for people who don't have the development and yum

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

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 enables the ability to take the ovirt-node-image iso and deploy it to an iscsi disk. It also provides a sample pxe configuration for booting based on the iscsi root device. Includes support for user/password as well as reverse chap user/password. --- Makefile.am | 1 + livecd-iso-to-iscsi | 201 ++++++++++++++++++++++++++++++++++++++++++++++ ovirt-node-image.spec.in |

Patch set fixes issues with image size increase when using edit-livecd Also address issue with ext4 root fs