similar to: RFC: Advanced Storage Configuration

This patch includes feedback from apevec to remain backward compatible with the previous karg, ovirt_local_boot.

Resending the refactored patch: I realized after I emailed it that it referenced the wrong bugzilla.

This patch adds a safety verification to configure_from_network function, where network configuration will not be performed if it is already up and running, preventing lost of communication for connections already established. Signed-off-by: Ricardo Marin Matinata <matinata at br.ibm.com> --- scripts/ovirt-early | 9 ++++++--- scripts/ovirt-functions | 7 +++++++ 2 files changed,

This fix enables the persistance of empty configuration files during firstboot, in ovirt_store_config, so configuration files like ssh/ssl keys that are dynamically generated (i.e. content is not known until the node has booted at least one time) to well known locations can be pre set for persistance. Signed-off-by: Ricardo Marin Matinata <matinata at br.ibm.com> ---

This fix enables the persistance of empty configuration files during firstboot, in ovirt_store_config, so configuration files like ssh/ssl keys that are dynamically generated to well known locations can be pre set for persistance. Signed-off-by: Ricardo Marin Matinata <matinata at br.ibm.com> --- scripts/ovirt-functions | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff

The following patches introduce support for multipath and cciss devices to the ovirt-node and node-image. Comments are appreciated. These patches assume that the 3 patches (2 node, 1 node-image) from Joey are all incorporated. Mike

not just console= This is to allow vendor-specific boot parameters to survive when the image is installed to disk. Signed-off-by: Alan Pevec <apevec at redhat.com> --- scripts/ovirt-early | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/ovirt-early b/scripts/ovirt-early index 4b85102..c17ea74 100755 --- a/scripts/ovirt-early +++ b/scripts/ovirt-early @@

This patch introduces the concept of an "Advanced Storage Configuration", specifically for automated installs (although it could be hooked into manual install), while preserving the original style of specifying LVs. It accomplishes the following: * Add an optional AppVG * Offer new optional LVs - Data2,Swap2 - as part of the new AppVG * Allows the specification of multiple disks, per VG

Hi I am running a pxe diskless node in f13 and I have some proposals to make ovirt-early working in this version. nash is no more available (nash/mkinitrd is replaced by dracut), so this following command fails : "echo "network --device $DEVICE --bootproto dhcp" | nash" it makes the network configuration incomplete. I replace the linuxrc command by dhclient and it's

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

(depends on Advance Storage Configuration patch) This patch adds the option of requesting, at install time, that swap LVs be encrypted. The modifications include: * Introduction of the ovirt_swap_encrypt install parameter * Inclusion of all required packages * Inclusion of required kernel modules * Introduction of /etc/ovirt-crypttab to hold encrypted swap configuration (Couldn't use

Creates an additional LV, CoreDump. This LV, if present, is mounted at /var/log/core. Its default size is 10240 MB (10G) and has a minimum size of 1024 MB. Additionally, the default log partition size was changed from 256 MB to 2048 MB (2G). Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-storage | 23 ++++++++++++++++++----- scripts/ovirt-early

This patch allows the node to be upgraded without destroying any configuration. The new kernel argument, ovirt_upgrade, will boot cause the node to install the upgraded image, then reboot. Resolves: rhbz#527217 Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-early | 14 +++++++------- scripts/ovirt-firstboot | 22 +++++++++++++---------

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

--- examples/create-disk.c | 20 +++++--------------- examples/mount-local.c | 22 +++++----------------- golang/examples/create-disk.go | 12 ++---------- ocaml/examples/create_disk.ml | 4 +--- perl/examples/create_disk.pl | 4 +--- python/examples/create_disk.py | 5 +---- ruby/examples/create_disk.rb | 4 +--- 7 files changed, 16 insertions(+), 55 deletions(-) diff

Would this work? The problem is, I do not have roaming profiles in use(As it is not practical for us, as users tend to use the same computers). I want only users with IP from 192.168.1.x to load the databases. The loaddatabases.cmd file in question would contain rem Grab IP address and dump to a file ipconfig >"%userprofile%\ipconfig.txt" echo Checking for your location

A lot of code runs 'qemu-img create' or 'truncate' to create blank disk images. In the past I resisted adding an API to do this, since it essentially duplicates what you can already do using other tools (ie. qemu-img). However this does simplify calling code quite a lot since qemu-img is somewhat error-prone to use (eg: don't try to create a disk called "foo:bar")

This hook script tries to address the fact that a RHEV-H installation will format all the storage devices available in the machine in order to create HostVG and AppVG with all the available space. It may be the case that RHEV-H needs to respect and co-exist with a proposed partitioning scheme, not getting all the storage space for HostVG and AppVG volume groups. The proposed solution adds the