ReleaseEngineering/PuppetAgain: Difference between revisions

ReleaseEngineering/PuppetAgain (view source)

20 bytes removed , 26 April 2013

canmove, Confirmed users

1,394

edits

@@ Line 126: / Line 126: @@
 == Puppetmasters ==
-Releng puppet masters are managed by IT (in fact, managed by IT's puppet infrastructure, which can lead to some confusion).  There will be as many puppet masters as required, attempting to minimize the need for communication across WAN links.  The puppet masters do not permit root logins by non-sysadmins, but automatically update from the manifest repository using a crontask.  As described below, masters also allow user logins for a limited set of people, who can set up puppet environments.
+PuppetAgain masters are managed by PuppetAgain.  Each organization can have 1 or more masters, arranged in a cluster.  There is one "distinguished master" in the cluster.  This master is distinguished only for purposes of simplifying synchronization -- the cluster will continue to operate indefinitely without the distinguished master, although master-master communication (secrets and CRLs) will not work.
 See the following for more details, noting that most of this is not required for an external PuppetAgain implementation.
@@ Line 133: / Line 133: @@
 * [[ReleaseEngineering/PuppetAgain/Base Images]]
 * [[ReleaseEngineering/PuppetAgain/Certificate Chaining]]
+* [[ReleaseEngineering/PuppetAgain/HowTo/Bootstrap a Puppetmaster]]
 == Puppet Versions ==