cauldron {
        should be a regular tool (i.e. a spell)
        config file (/etc/cauldron.conf)
        everything else in var (/var/state/cauldron /var/lib/cauldron etc.)
        modular design
        allow for multiple install interfaces (minimal shell, guided shell,
                dialog/ncurses/whatever term ui, graphical X installer,
                etc.)
        allow for different archs (x86, x86_64, ppc, alpha, sparc, etc.)
                spellsets specific to each arch (lilo/grub for x86,
                        yaboot for ppc, etc.)
        generic spellset? (maybe, depends on how much should get managed
                by arch specific spellsets)
        allow for different initrds (initrd, initramfs, etc.)
        script functions should be in function file(s),
                execution in exec file (like current init script setup)
        commands for basesystem creation, setting iso gen options (which
                installer interface, which arch, etc.), iso generation,
                etc.
        config/state dirs should be clean and names should be clear (i.e.
                cauldron/interface for installer interface files)
        interface ideas:
                batch mode (like kickstart for RH?)
                advanced console (drop to shell, nothing but a README
                        displayed for user, they are on their own)
                simple console (BearPerson's guided installer)
                gui console (dialog menu-based installer)
                graphical X (don't know what would be used yet,
                        but it's an idea...)
        installation methods:
                parallel (use the depends functionality in init
                        but for the install stages, easier once the
                        installer is modular)
                serial (simpler and more stable, but not as spiffy)
                batch (like parallel, but no need for depends info
                        since there are no questions to ask the user)
                pretend (prints what would be installed and how, but
                        doesn't actually install anything)
}

ideas:
iso spell/grimoire to automatically contain (and auto-update from stable) all the spells necessary for iso creation

cauldron-internal grimoire containing spells for e.g. everything in /etc that should be installed onto a first-time system, with all the defaults sensible for such an install
        -- spells for the iso installers themselves perhaps?

set up sub-projects in git for the different cauldron components?
        -- iso creation, iso installers, iso grimoire

iso installation "--pretend" mode for debug/test purposes

some kind of automated iso tester (prometheus for cauldron)
        having a --pretend will help for this

menu system for non-advanced things, console for advanced install steps
        need a way to update menu items based on what is done in console

Cauldron/Devel/Ideas (last edited 2010-02-24 07:56:14 by flux)