Changes

Jump to: navigation, search

ReleaseEngineering/PuppetAgain

20 bytes removed, 19:32, 26 April 2013
Puppetmasters
== Puppetmasters ==
Releng puppet PuppetAgain masters are managed by IT (in fact, managed by IT's puppet infrastructure, which can lead to some confusion)PuppetAgain. There will be as many puppet Each organization can have 1 or more masters as required, attempting to minimize the need for communication across WAN linksarranged in a cluster. The puppet masters do not permit root logins by non-sysadmins, but automatically update from There is one "distinguished master" in the manifest repository using a crontaskcluster. As described below, masters also allow user logins This master is distinguished only for a limited set purposes of peoplesimplifying synchronization -- the cluster will continue to operate indefinitely without the distinguished master, who can set up puppet environmentsalthough 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.
* [[ReleaseEngineering/PuppetAgain/Base Images]]
* [[ReleaseEngineering/PuppetAgain/Certificate Chaining]]
* [[ReleaseEngineering/PuppetAgain/HowTo/Bootstrap a Puppetmaster]]
== Puppet Versions ==
Canmove, confirm
1,394
edits

Navigation menu