canmove, Confirmed users
1,394
edits
ReleaseEngineering/PuppetAgain: Difference between revisions
Jump to navigation
Jump to search
→Base Images
(→Action) |
|||
| Line 112: | Line 112: | ||
The releng puppet infrastructure will be using the same puppet versions as the rest of Mozilla. This generally tracks the latest puppet release. As IT upgrades, the masters will be upgraded; releng can then upgrade the clients using puppet itself. | The releng puppet infrastructure will be using the same puppet versions as the rest of Mozilla. This generally tracks the latest puppet release. As IT upgrades, the masters will be upgraded; releng can then upgrade the clients using puppet itself. | ||
== Base Images == | == Base Images and Puppetizing == | ||
The base images for this infrastructure are barely-modified OS installs. They have just enough installed that they can connect to a puppet server, get certificates, and puppetize on boot. | The base images for this infrastructure are barely-modified OS installs. They have just enough installed that they can connect to a puppet server, get certificates, and puppetize on boot. | ||
See [[ReleaseEngineering/PuppetAgain/Base Images]] for more on the base images and the | See [[ReleaseEngineering/PuppetAgain/Base Images and Puppetizing]] for more on the base images and the puppetization process. Note that, while most of PuppetAgain is intended to be easily replicated, the deployment system is probably not easily replicated, and is best left out of any external implementations. | ||
== Data == | == Data == | ||