[Labs-l] Puppet docs (was: Re: This week's update, now with 7.3% more levity!)

[Dan Michael O. Heggø]

Thanks for the link, Silke. It's helpful, but not the kind of
practical guide aimed at tool maintainers I had in mind. It also
assumes that you have root access, but if I've understood it right the
average tool maintainer is not supposed to have that on the tools
project? Perhaps puppet is not supposed to be used by the average tool
maintainer, but it would be nice to clarify, as you say, when it makes
sense to puppetize and not, and what is considered "best practice" for
deploying a tool with some dependencies.

Dan Michael

On 12 March 2013 10:51, Silke Meyer <silke.meyer at wikimedia.de> wrote:
> Hi Dan,
>
> there is a documentation page for the development of one's own puppet
> recipes here:
> https://wikitech.wikimedia.org/wiki/Help:Self-hosted_puppetmaster
>
> Recently, I added some FAQ that were based on the questions I had myself
> and that were answered on this list.
>
> What would be cool to have on that page: The big picture.
> * When does it make sense to "puppetize" one's server configs? When does
> it not?
> * Advantages: From what I understand, there are two advantages: 1)
> quickly get rid of an instance and build a new one with a fresh setup,
> 2) get configs developed by parts of the crowd from Labs into
> production. Others?
>
> Obviously, you can all help to improve that page or post stuff in this
> thread that I will then add to the page.
>
> Cheers, Silke
>
>
> Am 12.03.2013 09:15, schrieb Dan Michael O. Heggø:
>> On 11 March 2013 22:09, Marc A. Pelletier <marc at uberbox.org> wrote:
>>> My plate this week is going to be occupied mostly with helping people with
>>> the new environment, setting up puppet classes to subsume the tools-
>>> instances' configuration, and writing documentation aimed at tool
>>> maintainers looking to join the project.  (The latter being driven a great
>>> deal by what the actual maintainers do in fact stumble on).
>>
>> When it comes to documentation, one thing I would love to see is a
>> short practical guide on puppet, aimed at tool maintainers on labs. I
>> keep seeing puppet mentioned all the time, and I understand that it's
>> used to manage the wikimedia servers and so on, but I've never found
>> the time to look into it, and it's not clear to me if it's something a
>> simple tool with a few dependencies can benefit from using. If the
>> guide could clarify this, it would be great. It would be nice to have
>> some example puppet files, and a guide on the process of comitting
>> them.
>>
>> Dan Michael
>>
>> _______________________________________________
>> Labs-l mailing list
>> Labs-l at lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/labs-l
>>
>
>
> --
> Silke Meyer
> Systemadministratorin und Projektassistenz Wikidata
>
> Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
> Tel. (030) 219 158 260
>
> http://wikimedia.de
>
> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
> unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt
> für Körperschaften I Berlin, Steuernummer 27/681/51985.
>
> _______________________________________________
> Labs-l mailing list
> Labs-l at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/labs-l