[Infrastructures] a day in the life of isconf

[Bennett Todd]

--/NkBOFFp2J2Af1nK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

2005-11-21T06:49:41 Anand Kumria:
> 	- what happens once you branch from the base.

It's as though you created a completely separate domain, with two
differences. First, all patches applied to the base up to the point
of branching are included in the branch, as the start of it's
transaction log. And second, if any base machines haven't had any
further transactions applied, they can be moved to the branch.

> 	Let's say a security update comes out, I can immediately put
> that on the base image -- can I then have the branch attempt to apply
> that same change to itself?

The base _image_ is never touched after you begin using isconf; all
changes from when you start using isconf are applied with isconf,
and a run of isconf at boot-time updates any new-built machine.

If you get a security update, and you've branched, you'll probably
want to apply the security update onto the base, and onto every
branch as well. N branches will probably mean N+1 applications of
the security update.

> 	- /etc/is/main.cf

I use a separate one for each isconf domain I set up. I've not yet
found any use for branches. All machines in the same domain have the
same main.cf.

-Bennett

--/NkBOFFp2J2Af1nK
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFDgcqLHZWg9mCTffwRAslAAKDcC5K++xdEMqp4hWmj0TVtr3gvbQCgg0ui
9FCLikNZgnSeQzavAXGzxWI=
=6k7R
-----END PGP SIGNATURE-----

--/NkBOFFp2J2Af1nK--