canmove, Confirmed users
1,394
edits
ReleaseEngineering/PuppetAgain: Difference between revisions
→System Description
| Line 15: | Line 15: | ||
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. | 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. | ||
See [[ReleaseEngineering/PuppetAgain/Puppetmasters]] | See the following for more details, noting that most of this is not required for an external PuppetAgain implementation. | ||
* [[ReleaseEngineering/PuppetAgain/Puppetmasters]] | |||
* [[ReleaseEngineering/PuppetAgain/Puppetization Process]] | |||
* [[ReleaseEngineering/PuppetAgain/Base Images]] | |||
* [[ReleaseEngineering/PuppetAgain/Certificate Chaining]] | |||
== Puppet Versions == | == Puppet Versions == | ||