[Pkg-puppet-devel] puppet version management
Anthony BERGER
anthony.berger at cea.fr
Wed Jul 28 10:43:45 UTC 2010
Anthony BERGER
Infogerance CEA Cadarache
Administrateur Linux/Unix
Tel : 04 42 25 78 46
Le 28/07/2010 10:57, Stig Sandbeck Mathisen a écrit :
> Anthony BERGER<anthony.berger at cea.fr> writes:
>
>
>> what is the best way to manage the debian puppet versions.
>> I have debian etch, lenny and next squeeze manage by puppet. (lots of
>> configuration)
>> My puppetmaster is running on a lenny server and can not be easily updated.
>>
>> what do you think is the best way to use squeeze client on the
>> existing infrastructure ?
>>
>> i think that my etch client will not work on squeeze master ? (not
>> like etch version on lenny master)
>>
>> can i easily repackage puppet and co ?
>>
> It looks like you could use your own repository.
>
> You can then take the puppet version from "unstable" or "experimental",
> and put it in your local repository for sqeeze, lenny and etch.
>
> The http://wiki.debian.org/HowToSetupADebianRepository link may be of
> use here. Both "reprepro" and "mini-dinstall" will work well.
>
> In addition, my manifests/site.pp lists which puppet agent versions I
> allow to connect, like this:
>
> ,----
> | case $puppetversion {
> | "0.24.8",
> | "0.25.4",
> | "0.25.5",
> | "2.6.0": {
> | }
> | default: {
> | fail("[$fqdn] Unsupported puppet agent version $puppetversion")
> | }
> | }
> `----
>
>
>
yes, i already use mini-dinstall... it work well for a little repo (but,
sometime very slow..! )
The problem with puppet is the unsupported all clients versions on an up
to date puppetmaster... !
Just Why ?
The master should know all old clients and manage the clients connexions
accordingly.
The case you told me should be an internal mechanism ?
no ?
More information about the Pkg-puppet-devel
mailing list