On 7/4/2010 11:17 AM, Tass Skoudros wrote:
Each has its own advantage and we will be using external nodes to load
the configurations in both cases. The differences are that the first
would quickly become an issue when the version of the puppet client
changes. So we have been exploring the second of these and still have
other encounters that break with our goal of full automation.
So my question, is there a better way? Am I missing something.
If you are using multiple puppetmasters and resource collection (using
@@ and <<||>> syntax) those all need to access the same database and
have to be the same version.
It is expected that a puppetmaster with version N can still serve up
configurations to clients of version N-1. That is, 0.24.x clients can
talk to 0.25.x servers and 0.25.x clients can talk to 2.6.x servers.
If you need longer deployment times of client versions, you're better
off keeping a matching puppetmaster around and looking at a manually
(e.g. cluster ssh) approach to upgrading over multiple versions in one
swoop.
Best Regards, David Schmitt
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
