[Infrastructures] isconf deprecates infrastructures.org?

[Steve Traugott]

On Sun, Aug 13, 2006 at 12:39:19PM -0700, Wil Cooley wrote:
> This has long been a complaint of mine with the tools I've looked at.
> I'd really like to be able to inform the tool, make local changes, then
> check my changes back into the central repository, easily and without a
> lot of fuss.  Because, invariably, it takes more than one try to get a
> particular configuration right and the iteration of "change in repo,
> manually run tool to update host, reload server, see if it worked" is
> frustratingly long--even if it's only 30 seconds or so.

The whole point of isconf 4 is to get rid of this cycle.  There is no
longer any gold server; no central repository.  You just do something
like this on one of the machines you want to change:

    # lock isconf on all hosts so nobody else can make changes 
    isconf -m "upgrade mutt" lock

    # take a snapshot of the new mutt package
    isconf snap /tmp/mutt_1.5.9-2_i386.deb

    # install it
    isconf exec dpkg -i /tmp/mutt_1.5.9-2_i386.deb

    # check it in, unlocking other hosts
    isconf ci

...then do this on other hosts to update them (I also put this in rc,
and sometimes in cron):

    # replay the above 'snap' and exec', as well as anything else queued up
    isconf up  

More details in the man page:

    http://trac.t7a.org/isconf/pub/doc/latest/isconf.html

Steve
-- 
Stephen G. Traugott  (KG6HDQ)
Managing Partner, TerraLuna LLC
stevegt@TerraLuna.Org -- http://www.t7a.org