[Infrastructures] a day in the life of isconf

[Anand Kumria]

Hi,

I'm in the process of setting up a greenfield infrastructure site, so I
thought I'd try something different to managing each individual machine.

I'm currently evaluating FAI, cfengine and, or course, ISconf.

While I understand the concepts and design decision behind ISconf I was
wondering if someone could explain:
	- what happens once you branch from the base.

	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?

	Or would I have to apply the change to each 'branch'? Perhaps a
sequence of commands would be instructive?

	- /etc/is/main.cf

	How are people managing this?  It seems it needs to be
hand-constructed for each machine.  In my case this site is small (~10
machines), so it isn't too big a deal but what about for larger sites?

Thanks,
Anand