canmove, Confirmed users
1,394
edits
ReleaseEngineering/PuppetAgain: Difference between revisions
no edit summary
No edit summary |
|||
| Line 101: | Line 101: | ||
* [[ReleaseEngineering/PuppetAgain/HowTo/Set up a user environment]] | * [[ReleaseEngineering/PuppetAgain/HowTo/Set up a user environment]] | ||
* [[ReleaseEngineering/PuppetAgain/HowTo/Add new secrets]] | * [[ReleaseEngineering/PuppetAgain/HowTo/Add new secrets]] | ||
* [[ReleaseEngineering/PuppetAgain/HowTo/Bootstrap a Puppetmaster]] | |||
* [[ReleaseEngineering/PuppetAgain/HowTo/Change secrets]] | * [[ReleaseEngineering/PuppetAgain/HowTo/Change secrets]] | ||
* [[ReleaseEngineering/PuppetAgain/HowTo/Build RPMs]] | * [[ReleaseEngineering/PuppetAgain/HowTo/Build RPMs]] | ||
| Line 116: | Line 117: | ||
== The Goals == | == The Goals == | ||
* PuppetAgain should be usable as a whole for folks outside of Mozilla, Inc. who want to build similar systems | * PuppetAgain should be usable as a whole for folks outside of Mozilla, Inc. who want to build similar systems (see "Organizations" below) | ||
* Client images should proceed automatically from base image install to a fully-operational state. While refimages may be employed, this is done only as an optimization. | * Client images should proceed automatically from base image install to a fully-operational state. While refimages may be employed, this is done only as an optimization. | ||
* We do not keep distinct reference images. Reference images are used only as an optimization to avoid pounding the puppet servers when installing dozens of new hosts. When a new refimage snapshot needs to be made, a fresh machine is rebuilt from scratch, snapshotted, and then returned to service. | * We do not keep distinct reference images. Reference images are used only as an optimization to avoid pounding the puppet servers when installing dozens of new hosts. When a new refimage snapshot needs to be made, a fresh machine is rebuilt from scratch, snapshotted, and then returned to service. | ||
| Line 123: | Line 124: | ||
* Documentation (here) is a part of the patch. | * Documentation (here) is a part of the patch. | ||
See [[ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain]] for more detail | See [[ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain]] for more detail | ||
== Organizations == | |||
Each distinct instance of puppetagain is referred to as an organization, and tagged with a short identifier (e.g., "moco" for the mozilla releng instance, or "seamonkey" for seamonkey). Within an organization, configuration and secrets are shared, and everything runs from the same set of manifests. Configuration and secrets can differ between organizations. | |||
== Puppetmasters == | == Puppetmasters == | ||
| Line 131: | Line 136: | ||
* [[ReleaseEngineering/PuppetAgain/Puppetmasters]] | * [[ReleaseEngineering/PuppetAgain/Puppetmasters]] | ||
* [[ReleaseEngineering/PuppetAgain/Puppetization Process]] | * [[ReleaseEngineering/PuppetAgain/Puppetization Process]] | ||
* [[ReleaseEngineering/PuppetAgain/Certificate Chaining]] | * [[ReleaseEngineering/PuppetAgain/Certificate Chaining]] | ||
* [[ReleaseEngineering/PuppetAgain/HowTo/Bootstrap a Puppetmaster]] | * [[ReleaseEngineering/PuppetAgain/HowTo/Bootstrap a Puppetmaster]] | ||