Re: isconf deprecates infrastructures.org?
Steve Traugott <stevegt <at> TerraLuna.Org>
2006-09-19 02:00:11 GMT
On Sun, Aug 13, 2006 at 12:48:20AM -0700, Mark Ferlatte wrote:
> 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.
Systemimager during reboot running from a miniroot is always going to
be a reliable rollback -- it's what I use with isconf. But
systemimager's updateclient script is a different animal, since it
runs in the context of the machine it's modifying. Updateclient is
not going to be reliable in those cases where it (or anything else)
modifies systemimager or any of its prereqs, such as rsync, perl,
libc, init scripts, the kernel, etc. While this might be fine in
development environments, I don't use it in production. Since I
always manage production and development machines the same way, this
means I don't use updateclient at all.
By the way, I just noticed a serious bug in updateclient; the rsync
command is missing the -H and -S flags. I had the rsync guys fix this
in getimage and the miniroot years ago; looks like they never fixed it
So, when running updateclient, you are in fact guaranteed to *not* get