On 12/28/2011 05:12 PM, Michael Gliwinski wrote: > On Wednesday 28 Dec 2011 14:07:30 Nick Anderson wrote: >> On 12/28/2011 07:13 AM, Michael Gliwinski wrote: >>> Another option which I'm considering now is to let managed nodes pull >>> from VCS directly into their own masterfiles and change policy in >>> update.cf to just copy locally into inputs/ modules/ etc. after doing >>> some local >>> processing/verification. Any disadvantages? >> You might run into vertical scale issues for your version control server >> being able to be the master for lots of clients. I use this approach for >> some things on a small scale, beyond a few nodes I usually have one of >> those few nodes act as a master for the files that are checked out from >> version control. > Wouldn't that also be a problem for single cfengine "master" server (i.e. cf- > serverd)? > >
cf-serverd might cope a little better than a version control server, as it was designed to handle load, whereas a version control server expects far less traffic. I personally think that checking directly out of svn is risky because you might accidentally commit something broken. The more manual checks in between version control and deployment the better, in my cautious view. M -- CTO and Founder CFEngine http://www.cfengine.com http://www.markburgess.org _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
