Announcing Foreman Discovery oVirt-based image

Hello Foreman developers,

TL;DR

There is a new Discovery image available based on Red Hat systems. To
test it out do this on your TFTP:

cd /var/lib/tftpboot/boot
wget http://lzap.fedorapeople.org/zzz/discovery-initrd.img
wget http://lzap.fedorapeople.org/zzz/discovery-vmlinuz

And configure your PXE Default (the last line was wrapped):

DEFAULT menu
PROMPT 0
MENU TITLE PXE Menu
TIMEOUT 200
TOTALTIMEOUT 6000
ONTIMEOUT discovery

LABEL discovery
MENU LABEL Foreman Discovery
KERNEL boot/discovery-vmlinuz
APPEND rootflags=loop initrd=boot/discovery-initrd.img
root=live:/foreman.iso rootfstype=auto ro rd.live.image rd.live.check
rd.lvm=0 rootflags=ro crashkernel=128M elevator=deadline max_loop=256
rd.luks=0 rd.md=0 rd.dm=0 foreman.ip=192.168.122.1 selinux=0 stateless

FULL ANNOUNCEMENT

Recently I and Greg have been working on new image for Foreman Discovery
plugin. The original is based on Tiny Core Linux, which is a great
embedded solution. But we always wanted to provide another
enterprise-grade image with all the possible enterprise drivers and
firmware available.

There is a project called oVirt Node (1) that provides tools and
blueprints for building own Fedora/RHEL based memory-only images. It
supports stateless and stateful mode and provides several options how to
build images, including possibility to "inject" plugins into existing
images.

So we made a plugin! It's called Foreman Discovery oVirt Node Plugin
"doh" (2) and today, it is available in the Foreman Discovery git (3)
and (4). It is slightly bigger than TCL image (about 170 MB
kernel+initrd), but this can be seen as a starting point. There is an
excellent mechanism called minimizer-scripts which allows us to drop
packages, files or directories from the image easily.

Along with TCL image, you can build your own oVirt-based images today.
There are some limitations tho, but everything is properly documented.
We currently tested only images based on Fedora 19, we plan to support
RHEL6-based images as well. Although it is possible to "inject" foreman
plugin into existing image, this will work with oVirt 3.1 or higher
which has not been released yet. Therefore to build your own image, you
need to build oVirt base image first from git. Everything is on the
wiki.

Important note - we are not changing how Foreman Discovery works. The
image contains the same code and the only difference is the delivery
platform.

We are also providing pre-built F19 images you can immediately start
playing with (5). For a building quick start, head over to (6). The
foreman ovirt node plugin lives here (4).

We are looking for your comments and patches.

Links:

(1) http://www.ovirt.org/Category:Node
(2) http://www.youtube.com/watch?v=g6GuEswXOXo
(3) https://github.com/theforeman/foreman_discovery
(4) https://github.com/theforeman/foreman_discovery/tree/develop/extra/ovirt-node-plugin-foreman
(5) https://github.com/theforeman/foreman_discovery/blob/develop/README.ovirt_image.md#downloading-existing-discovery-pxe-image
(6) https://github.com/theforeman/foreman_discovery/blob/develop/README.ovirt_image.md#building-the-discovery-pxe-image

··· -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman