[Labs-l] Self Hosted puppetmaster with puppet clients?

[Andrew Otto]

> would it be possible for the the puppet manifests to live in the shared project storage?
Hm, true, that would be just as good.  This is probably possible to to manually on each of your machines.  symlink /var/lib/git/operations/puppet to /data/project/puppet (or whatever).  Right?



On Apr 3, 2013, at 2:32 PM, Kai Krueger <kakrueger at gmail.com> wrote:

> On 04/03/2013 09:16 AM, Andrew Otto wrote:
>> Hi yalls,
>> 
>> Analytics will soon be working on a kraken labs project.  We'd like to have a few nodes there, probably starting with 5, but possibly up to 10ish.
> The maps project is, I think, in a similar situation. We are trying to set up a multi-server setup to test various server configurations with puppet and fail-over and scaling procedures before moving it to production. 
>> 
>> Is it possible/allowed to set up self-hosted puppetmaster on a single one of these nodes, and have the other puppet clients point at it?  This way we wouldn't have to make modifications to /var/lib/git/operations/puppet on all of the nodes when we want to run puppet.
> Alternatively, would it be possible for the the puppet manifests to live in the shared project storage? E.g. at /data/project/puppet? That way all instances of the project would see a shared view of the files and when you spin up a new instance it would use the appropriately modified puppet files from the get go. This would be similar to the self hosted debian repository that lives in /data/project/repo, which is rather useful.
> 
> Kai
>> 
>> -Ao
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/labs-l/attachments/20130403/eb2cf469/attachment.html>