<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 04/03/2013 09:16 AM, Andrew Otto
wrote:<br>
</div>
<blockquote
cite="mid:%3C6B3E9AF5-8A3A-4356-9CF7-A11163A6DA20@wikimedia.org%3E"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div>Hi yalls,<br>
<font color="#0f61c8"><br>
</font>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.<br>
</div>
</blockquote>
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. <br>
<blockquote
cite="mid:%3C6B3E9AF5-8A3A-4356-9CF7-A11163A6DA20@wikimedia.org%3E"
type="cite">
<div><font color="#0f61c8"><br>
</font>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.<br>
</div>
</blockquote>
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.<br>
<br>
Kai<br>
<blockquote
cite="mid:%3C6B3E9AF5-8A3A-4356-9CF7-A11163A6DA20@wikimedia.org%3E"
type="cite">
<div><font color="#0f61c8"><br>
</font>-Ao<br>
<br>
</div>
</blockquote>
<br>
</body>
</html>