In its current state, the CLI tools require the user to strictly follow
the supported templates and specify *all* the options and sections --
even if they are blank. Even for the Web UI, the config file is
generated such that it follows this template strictly. That is not very
As a first step towards changing this to allow the config file to have
only the bare minimum required for building images, I have created a
list of the three tools used to create boot, DVD and live images with
their mandatory, optional with no sensible defaults, optional with
sensible defaults and switches. The list can be found at . Please
correct if there is anything I may have got wrong.
Is it fair to assume that only the mandatory options as required by the
original tools should also be the only ones supported by the build
service as well?
Once this list is decided, the CLI and the WebUI can assume the original
sensible defaults or change them to a pre-decided default values for the
others, in case they are not specified.
 I have plans for a config file generator script.
Thanks for any inputs.
Amit Saha <http://echorand.me>
Infrastructure Engineering and Development
Red Hat, Inc.