foreman_discovery 1.1.1 → 1.2.0.rc1

data/extra/ovirt-node-plugin-foreman/COPYING

@@ -0,0 +1,340 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+     51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year  name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.

data/extra/ovirt-node-plugin-foreman/Makefile.am

@@ -0,0 +1,60 @@
+# vim: ts=8:sw=8:noet
+#
+# Copyright (C) 2013 Red Hat, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; version 2 of the License.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+# MA  02110-1301, USA.  A copy of the GNU General Public License is
+# also available at http://www.gnu.org/copyleft/gpl.html.
+
+OVIRT_CACHE_DIR	?= $(HOME)/ovirt-cache
+
+PYTHONSOURCES = \
+	$(shell find scripts -name \*.py)
+
+SHELL := /bin/bash
+
+SUBDIRS = \
+	conf \
+	src \
+	recipe
+
+EXTRA_DIST = \
+	ovirt-node-plugin-foreman.spec \
+	ovirt-node-plugin-foreman.spec.in
+
+DISTCLEANFILES = $(PACKAGE)-$(VERSION).tar.gz \
+	aclocal.m4 \
+	configure \
+	install-sh \
+	missing
+
+DISTCLEANDIRS = autom4te.cache
+
+rpms: dist
+	rpmbuild $(RPM_FLAGS) -ta $(distdir).tar.gz
+
+srpms: dist
+	rpmbuild $(RPM_FLAGS) -ts $(distdir).tar.gz
+
+publish: rpms
+	mkdir -p $(OVIRT_CACHE_DIR)
+	rsync -aq $(shell rpm --eval '%{_rpmdir}')/ $(OVIRT_CACHE_DIR)/ovirt/
+	rsync -aq $(shell rpm --eval '%{_srcrpmdir}')/ $(OVIRT_CACHE_DIR)/ovirt/src
+	createrepo $(OVIRT_CACHE_DIR)/ovirt
+
+iso: publish
+	cd recipe
+	make node
+
+.PHONY: rpms publish srpms

data/extra/ovirt-node-plugin-foreman/README.md

@@ -0,0 +1,217 @@
+Foreman Discovery oVirt Node Plugin
+===================================
+
+There are couple of options how to get a oVirt Node Discovery image:
+
+* Downloading existing one is the easiest method, but the image does not
+  provide site-specific options.
+
+* Downloading existing oVirt Node base image and injecting plugin into it.
+  This is the recommended process of creating your own image. It is fast and
+  still provides great flexibility of customization of the resulting image.
+
+* Building own oVirt Node base image and injecting the plugin into it. This
+  option must be used if you want to play with latest and greatest base image.
+
+All three processes are described on this page.
+
+Downloading image
+-----------------
+
+We provide download links on the [Foreman Discovery plugin
+page](https://github.com/theforeman/foreman_discovery).
+
+Injecting into existing base image
+----------------------------------
+
+Warning: This process will set SELinux to permissive mode during the build of
+new iso image. Since this can compromise security, it is highly recommended to
+use dedicated VM guest for building images.
+
+Although it is not possible to use stable version (3.0) for a base image,
+there are couple of [nightly
+builds](http://resources.ovirt.org/releases/node-base/nightly/iso/) that can
+be used. It seems any image from version 3.0.3 can be used.
+
+Discovery image 0.3.0 is built from 0.3.0-1.1.fc19 base iso image:
+
+    wget http://resources.ovirt.org/releases/node-base/nightly/iso/ovirt-node-iso-3.0.3-1.1.fc19.iso
+
+We plan to release Fedora and RHEL based discovery images built from oVirt
+Node stable version 3.1.
+
+Building the base image from git
+--------------------------------
+
+Building the discovery image involves two main steps:
+
+ * Building base oVirt Node ISO from git.
+ * Building the discovery plugin and inserting it into the existing ISO.
+
+Follow instructions on [oVirt
+wiki](http://www.ovirt.org/Node_Building#From_Git) to build the base oVirt
+Node ISO. Before proceeding, check the instruction on the oVirt page as they
+may change in future. What we have here might be different when using master.
+
+We are using clean VM guest of Fedora 19 and directly from root account. If
+you want to build using different user, check out the building instructions
+above and setup sudo for some commands. Make sure you have at least 4 GB of
+free space on the partition you are building on.
+
+First of all, fetch ovirt-node utilities and image builder:
+
+    git clone http://gerrit.ovirt.org/p/ovirt-node.git
+    git clone http://gerrit.ovirt.org/p/ovirt-node-iso.git
+
+Build ovirt-node packages:
+
+    export OVIRT_NODE_BASE=$PWD
+    export OVIRT_CACHE_DIR=~/ovirt-cache
+    export OVIRT_LOCAL_REPO=file://${OVIRT_CACHE_DIR}/ovirt
+    mkdir -p $OVIRT_CACHE_DIR
+    yum install livecd-tools appliance-tools-minimizer fedora-packager \
+        python-devel rpm-build createrepo selinux-policy-doc checkpolicy \
+        selinux-policy-devel autoconf automake python-mock python-lockfile
+    cd $OVIRT_NODE_BASE
+    cd ovirt-node
+    export EXTRA_RELEASE=.foreman
+    ./autogen.sh --with-image-minimizer
+    make publish
+
+Build the base image and move it to the base directory:
+
+    cd $OVIRT_NODE_BASE
+    cd ovirt-node-iso
+    ./autogen.sh --with-recipe=$OVIRT_NODE_BASE/ovirt-node/recipe
+    make iso
+    mv ovirt-node-iso-*.iso $OVIRT_NODE_BASE/
+
+Now we are ready to inject our plugin.
+
+*Troubleshooting*
+
+If you encounter any problem during build, check internet connection first
+and try again. Occasionally, package cannot be downloaded from a nearest
+mirror so the process can fail. If the problem persists, you can try with
+exact githash or tag we were building from:
+
+    cd ovirt-node
+    make distclean
+    git checkout 2e54ec17b55e1ee80
+    cd ../ovirt-node-iso
+    make distclean
+    git checkout 5ac5557fc5521d644
+    cd ..
+
+Also note that *building EL6 image (even on EL6 guest builder) is not
+supported* right now.
+
+Building and injecting the discovery plugin
+-------------------------------------------
+
+This second phase must be done on the same machine where base image was built.
+Please do not clean ovirt-node and cache directory as it is being used here.
+
+Building the plugin is much faster than building the base ISO and you can
+repeat this step more times. The base (source) ISO file will not get modified
+so you do not need to create any backup.
+
+Whole process can be described:
+
+ * Discovery plugin is build as an RPM and copied to `OVIRT_CACHE` directory.
+ * Base ISO is unpacked, mounted.
+ * Discovery RPM plugin is installed into the image making necessary changes.
+ * Many packages are uninstalled from the image shrinking size down to 170MB.
+ * Image is cleaned and wrapped back as ISO with ".foreman." version tag.
+ * Kernel image and init ram disk is extracted from the ISO.
+
+First of all we build plugin RPMs. Before that, we are going to clear the
+RPMSDIR directory just to make sure it's clean and publish it to the cache repository.
+
+    cd $OVIRT_NODE_BASE
+    RPMSDIR=$(rpm --eval '%{_rpmdir}')
+    rm -f $RPMSDIR/noarch/*rpm
+    git clone https://github.com/theforeman/foreman_discovery.git
+    cd foreman_discovery/extra/ovirt-node-plugin-foreman
+    ./autogen.sh
+    make rpms
+
+Now, let's modify the base ISO image and install the plugin there.
+
+    cd $OVIRT_NODE_BASE
+
+Create a new repo file in this directory with the following contents.
+
+    cat > ./foreman.repo <<'EOF'
+    [fedora-edit-node]
+    name=Fedora $releasever - $basearch
+    failovermethod=priority
+    baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
+    #mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch
+    enabled=1
+    gpgcheck=1
+    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
+
+    [updates-edit-node]
+    name=Fedora $releasever - $basearch - Updates
+    failovermethod=priority
+    baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/
+    #mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releasever&arch=$basearch
+    enabled=1
+    gpgcheck=1
+    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
+
+    [foreman]
+    name=Foreman nightly
+    baseurl=http://yum.theforeman.org/nightly/f19/$basearch
+    enabled=1
+    gpgcheck=0
+    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-foreman
+    EOF
+
+These three repositories will be used to install extra packages from Fedora 19
+and also Foreman Proxy from nightly repository. You can switch to Foreman 1.3+
+stable repository if you want. Injection is easy and quite fast:
+
+    ovirt-node/tools/edit-node \
+        --repo foreman.repo \
+        --nogpgcheck \
+        --install $RPMSDIR/noarch/ovirt-node-plugin-foreman-0*.rpm \
+        --verbose \
+        --debug \
+        ovirt-node-iso-*.iso
+    mv -f ovirt-node-iso-*.foreman.*.iso foreman.iso
+    test -d tftpboot && rm -rf tftpboot
+    livecd-iso-to-pxeboot foreman.iso
+
+Note we are renaming the target ISO to foreman.iso prior extracting kernel and
+initrd, otherwise you'd need to change kernel boot options.
+
+Finally, it's the time to copy those files to TFTP server:
+
+    scp tftpboot/initrd0.img root@tftp_server:/var/lib/tftpboot/boot/discovery-initrd.img
+    scp tftpboot/vmlinuz0 root@tftp_server:/var/lib/tftpboot/boot/discovery-vmlinuz
+
+Setup Foreman templates
+-----------------------
+
+Read instructions about how to setup Foreman and PXE on the following pages:
+
+* [Foreman Discovery oVirt Node instructions](../../README.ovirt_image.md)
+* [Foreman Discovery instructions](../../README.md)
+
+Development
+-----------
+
+The image is locked down, the root account is locked and there is no ssh
+daemon running on the image. But all of this can be enabled and few more
+command line utilities can be installed, if the plugin is configured with this
+option:
+
+    make distclean
+    ./autogen.sh --enable-debug
+
+The root password is set to "development" and ssh daemon is listening on the
+standard port. Also logging of discover-host and foreman-proxy services is
+increased to DEBUG level. See /tmp directory.
+

data/extra/ovirt-node-plugin-foreman/autogen.sh

@@ -0,0 +1,66 @@
+#!/bin/sh
+# Run this to generate configure and Makefile
+
+srcdir=`dirname $0`
+test -z "$srcdir" && srcdir=.
+
+THEDIR=`pwd`
+(
+  cd $srcdir
+  die=0
+
+  (autoconf --version) < /dev/null > /dev/null 2>&1 || {
+    echo
+    echo "You must have autoconf installed."
+    echo "Download the appropriate package for your distribution,"
+    echo "or see http://www.gnu.org/software/autoconf"
+    die=1
+  }
+
+  # Require libtool only if one of of LT_INIT,
+  # AC_PROG_LIBTOOL, AM_PROG_LIBTOOL is used in configure.ac.
+  grep -E '^[[:blank:]]*(LT_INIT|A[CM]_PROG_LIBTOOL)' configure.ac >/dev/null \
+      && {
+    (libtool --version) < /dev/null > /dev/null 2>&1 || {
+    echo
+    echo "You must have libtool installed."
+    echo "Download the appropriate package for your distribution,"
+    echo "or see http://www.gnu.org/software/libtool"
+    die=1
+    }
+  }
+
+  (automake --version) < /dev/null > /dev/null 2>&1 || {
+    echo
+    die=1
+    echo "You must have automake installed."
+    echo "Download the appropriate package for your distribution,"
+    echo "or see http://www.gnu.org/software/automake"
+  }
+
+  test $die = 1 && exit 1
+
+  test -f ovirt-node-plugin-foreman.spec.in || {
+    echo "You must run this script in the top-level directory"
+    exit 1
+  }
+
+  if test -z "$*"; then
+    echo "I am going to run ./configure with no arguments - if you wish "
+    echo "to pass any to it, please specify them on the $0 command line."
+  fi
+
+  aclocal
+
+  # Run autoheader only if needed
+  grep '^[[:blank:]]*AC_CONFIG_HEADERS' configure.ac >/dev/null && autoheader
+
+  automake --add-missing
+  autoconf
+  ./configure "$@"
+)
+
+if test "x$OBJ_DIR" != x; then
+    mkdir -p "$OBJ_DIR"
+    cd "$OBJ_DIR"
+fi