[Infrastructures] isconf deprecates infrastructures.org?

Mark Ferlatte ferlatte@cryptio.net
Sun, 13 Aug 2006 00:48:20 -0700


--n8g4imXOkfNTN/H1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Daniel Hagerty said on Sun, Aug 13, 2006 at 03:36:55AM -0400:
>     It's a pretty standard problem for sysadmin tools in this space.
> You'd have to detect what was done behind the tool's back and either
> pretend the missing delta was performed by the tool, or undo what was
> done outside the tool.  You're not going to get this kind of behavior
> from the isconf model of how you do things.

Dang.  That's too bad.  I'd kind of like to be able to use isconf
instead of the in-house system I'm using now (basically, systemimager's
updateclient + cvsup to overlay configurations), but we use the "reset
the system back to known baseline" functionality a lot.

=46rom reading more, it also seems like isconf assumes that your
environment never changes?  At least, there doesn't seem to be any way
to "collapse" the journal into a new base image so that you don't have
to replay the whole thing every time you image a new host.  In my case,
our current images are 2+ years old (Debian sarge), and there have been
a lot of things done to them in that period; having to replay 2 years of
changes (security patching apache multiple times, etc) every time I want
to install another rack of hosts doesn't seem like a good idea,
especially if someone removes a CNAME that hasn't been used for two
years but an early step in the journal depends on.

M

--n8g4imXOkfNTN/H1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFE3tlEOtZWu2tc1lARAnT3AKCHYPq/DnMF4Ka86HYFPXuWAZ1htQCaAqGn
qrXsvntunoMvRk/G+Usx4KA=
=wjlN
-----END PGP SIGNATURE-----

--n8g4imXOkfNTN/H1--