Lorax is a set of tools used to create bootable images.
Go to file
Brian C. Lane 5c878a695f Add --test option to composer-cli
The API server will run a mock compose when a test mode is passed to it.
Passing a 1 will queue a build, pretend to run the build for 10 seconds,
and then fail. Passing a 2 will do the same thing, but it will finish as
if it was successful. All results are available but the output file is
only the string "TEST IMAGE"

This should allow running tests inside docker without calling anaconda
(becuase it will not run in docker, it needs a VM).
2018-06-11 16:54:58 -07:00
docs lorax-composer: Add partitioned-disk output support 2018-06-11 16:54:58 -07:00
etc Add support for yum to lorax-composer 2018-06-11 16:54:58 -07:00
rel-eng Automatic commit of package [lorax] release [19.7.10-1]. 2018-06-11 16:54:58 -07:00
share Add the partitioned-disk.ks file for the new output type 2018-06-11 16:54:58 -07:00
src Add --test option to composer-cli 2018-06-11 16:54:58 -07:00
systemd Open the git repo after dropping root privileges 2018-06-11 16:54:58 -07:00
tests Make sure lorax-composer tests only use temporary directories 2018-06-11 16:54:58 -07:00
utils Don't redefine variables from outer scope 2018-06-11 16:54:57 -07:00
.coveragerc Measure coverage for parallel processes 2018-06-11 16:54:58 -07:00
.dockerignore Update how we pass the source to docker so it includes docs/ dir 2018-06-11 16:54:58 -07:00
.gitignore Add composer-cli utility and implement the recipes commands 2018-06-11 16:54:58 -07:00
.travis.yml Properly report coverage 2018-06-11 16:54:58 -07:00
ANNOUNCE Added draft on initial announce email as I keep adding to it. 2008-10-06 09:51:01 -10:00
AUTHORS add wwoods to AUTHORS 2011-10-26 12:36:06 -04:00
COPYING Initial project description files imported. 2008-09-11 14:16:39 -10:00
Dockerfile.test Install anaconda-tui in the test Docker image 2018-06-11 16:54:58 -07:00
epel.repo Enable testing in Travis CI using Docker container 2018-06-11 16:54:58 -07:00
lorax.spec Add composer-cli utility and implement the recipes commands 2018-06-11 16:54:58 -07:00
Makefile Add some tests for composer-cli 2018-06-11 16:54:58 -07:00
POLICY Update TODO and POLICY to reflect the current state of things 2012-01-06 14:41:21 -05:00
README Initial project description files imported. 2008-09-11 14:16:39 -10:00
README.livemedia-creator Document kickstart restrictions on %include (#1418500) 2017-08-11 15:11:30 -07:00
README.product Update docs for product.img (#1272361) 2016-02-19 16:41:58 -08:00
setup.py Add composer-cli utility and implement the recipes commands 2018-06-11 16:54:58 -07:00
TODO Update TODO and POLICY to reflect the current state of things 2012-01-06 14:41:21 -05:00

I am the Lorax.  I speak for the trees [and images].

Tree building tools such as pungi and revisor rely on 'buildinstall' in
anaconda/scripts/ to produce the boot images and other such control files
in the final tree.  The existing buildinstall scripts written in a mix of
bash and Python are unmaintainable.  Lorax is an attempt to replace them
with something more flexible.


EXISTING WORKFLOW:

pungi and other tools call scripts/buildinstall, which in turn call other
scripts to do the image building and data generation.  Here's how it
currently looks:

   -> buildinstall
       * process command line options
       * write temporary yum.conf to point to correct repo
       * find anaconda release RPM
       * unpack RPM, pull in those versions of upd-instroot, mk-images,
         maketreeinfo.py, makestamp.py, and buildinstall

       -> call upd-instroot

       -> call maketreeinfo.py

       -> call mk-images (which figures out which mk-images.ARCH to call)

       -> call makestamp.py

       * clean up


PROBLEMS:

The existing workflow presents some problems with maintaining the scripts.
First, almost all knowledge of what goes in to the stage 1 and stage 2
images lives in upd-instroot.  The mk-images* scripts copy things from the
root created by upd-instroot in order to build the stage 1 image, though
it's not completely clear from reading the scripts.


NEW IDEAS:

Create a new central driver with all information living in Python modules.
Configuration files will provide the knowledge previously contained in the
upd-instroot and mk-images* scripts.


-- 
David Cantrell <dcantrell@redhat.com>