On Wed, 28 Dec 2011 13:13:13 +0000 Michael Gliwinski <michael.gliwin...@henderson-group.com> wrote:
MG> Another option which I'm considering now is to let managed nodes MG> pull from VCS directly into their own masterfiles and change policy MG> in update.cf to just copy locally into inputs/ modules/ etc. after MG> doing some local processing/verification. Any disadvantages? I've done this with Git (which, unlike Subversion, is very light-weight) and thousands of hosts pulling hourly. The server load was very low using the Git smart protocol over HTTP and I did not have to set up any cfservd infrastructure. So in terms of resources, I'd say this is actually less of a burden than cfservd. The biggest disadvantage is that it's hard to hide information selectively from hosts--they all clone the whole repository, including its history. There are ways around this, if the approach appeals to you, but it's not trivial. Consistency checking is built into Git. Similarly, you can use Git branches to promote changes selectively. I used master for dev work, then there was a "qa" branch used by QA machines, a pre-release branch, and a release branch. Depending on the build process you use, it may make sense to add integration and unit testing stages, but the point is that it's pretty easy if you know Git. Ted _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
