The general rule of thumb is that your master must be at a version , like
Peter said, greater-than-or-equal-to your clients.
As far as backward compatibility, we strive to maintain a single major
release for backwards compatibility (i.e. a 2.7.x master would be
backwards-compatible with 2.6.x clie
Markus, yes. As long as the master's version is equal to or greater than the
agents, it will work. I can't speak for future master releases, though.
-- Peter (from phone)
On Mar 16, 2012, at 5:42 PM, Markus Falb wrote:
> On 13.3.2012 00:22, vagn scott wrote:
>> On 03/12/2012 10:16 AM, Peter Bu
On 13.3.2012 00:22, vagn scott wrote:
> On 03/12/2012 10:16 AM, Peter Bukowinski wrote:
>>
>> Your master's version should always be equal to or greater than the
>> latest client version you're using. You can count on a newer master
>> working with older clients, but don't count on newer clients wo
On 03/12/2012 10:16 AM, Peter Bukowinski wrote:
Your master's version should always be equal to or greater than the
latest client version you're using. You can count on a newer master
working with older clients, but don't count on newer clients working
with older masters.
So, no problems
Well, that's more than I expected. I can easily ensure that my server is
up-to-date, and then use whatever package I find for the agents...
Thanks.
Le lundi 12 mars 2012 15:16:32 UTC+1, pmbuko a écrit :
>
> On Mar 12, 2012, at 10:03 AM, Julien C. wrote:
>
> Hi,
>
> Due to severe heterogeneity am
On Mar 12, 2012, at 10:03 AM, Julien C. wrote:
> Hi,
>
> Due to severe heterogeneity among my servers (OS and version), I started my
> puppet infrastructure by deploying agents by hand (from the tarball). That
> way, I'm sure that I have the same version everywhere.
>
> Having found up-to-date