On 1 Nov 2006, at 19:55, Narayan Desai wrote:
"Paul" == Paul Anderson <[EMAIL PROTECTED]> writes:
Luke> what I am currently looking for is a way to keep the configs
Luke> in cvs or similar, then automatically deply first to test,
Luke> then to production.
We actually have a paper in at LISA this year about using this
sort of technique with bcfg2. There are a bunch of corner cases
that makes this a little tricky, but there are a ton of nifty
things that you can do (including configuration transactions and
workflows) if you do it right.
Paul> We have been doing this for a while. Recently, it has been
Paul> formalised more & we now have several different flavours of
Paul> machines with different levels of "stability". Production
Paul> machines get a weekly update which has been in test on
Paul> "development" machines for the previous week.
Out of curiosity, does the LCFG server know anything about the
revision control system, or is the change management functionality
handled entirely externally?
It is external. I think it is possible to write conditionals which
depend on the release version, but that doesn't seem like a good idea.
Of course, the individual aspects (headers) are version controlled
separately, so it is possible to pull back a particular aspect if you
screw something up, but the important thing here is to create a
stable, labeled configuration point for the whole site.
Paul
_______________________________________________
lssconf-discuss mailing list
lssconf-discuss@inf.ed.ac.uk
http://lists.inf.ed.ac.uk/mailman/listinfo/lssconf-discuss
