rpm-ostree
==========

This tool takes a set of packages, and commits them to an
[OSTree](https://wiki.gnome.org/Projects/OSTree) repository.  At the
moment, it is intended for use on build servers.

Using rpm-ostree
----------------

There are two levels; the core "rpm-ostree" command takes a set of
packages and commits them to an OSTree repository.

The higher level rpm-ostree-autobuilder parses a "products.json" which
generates potentially many filesystem trees.  It also has code to
generate disk images and run smoketests.


Installing and setting up a repository
--------------------------------------

First, unfortunately you must *disable* SELinux on the build host in
order to *support* SELinux on the built system.  See:
https://bugzilla.redhat.com/show_bug.cgi?id=1060423

Second, you must install `nss-altfiles` on the host system, and
edit your /etc/nsswitch.conf to include `altfiles`, like this:

	passwd: files altfiles 
	group:  files altfiles

You may or may not be using SSSD (and thus the `sss` option); if you
are then it should look like:

	passwd: files altfiles sss
	group:  files altfiles sss

For more information, see:
http://lists.rpm.org/pipermail/rpm-maint/2014-January/003652.html

There are packages available in the rpm-ostree COPR:
http://copr-fe.cloud.fedoraproject.org/coprs/walters/rpm-ostree/

At the moment, all of the tooling except for the patched
`shadow-utils` is in Fedora rawhide.

Once you have that done, choose a build directory.  Here we'll use
/srv/rpm-ostree.

	# cd /srv/rpm-ostree
	# mkdir repo
	# ostree --repo=repo init --mode=archive-z2


Running rpm-ostree
------------------

The core "rpm-ostree" takes as input a "treefile".  There is a demo
one in `doc/demo-treefile.json`.

	# rpm-ostree create sometreefile.json

All this does is use yum to download RPMs from the referenced repos,
and commit the result to the OSTree repository, using the ref named by
`ref`.

You can export `/srv/rpm-ostree/repo` via any static webserver.

Running the autobuilder
-----------------------

The autobuilder instead takes as input a `products.json` which
generates *multiple* treefile internally.  Try this:

	# ln -s /path/to/rpm-ostree.git/fedostree/products.json .
	# rpm-ostree-autobuilder

That will automatically poll every hour for changes in the RPMs
referenced by the `products.json` file, commit them to the
`/srv/rpm-ostree/repo`, and generate cached disk images in
`/srv/rpm-ostree/images`.