canmove, Confirmed users
1,394
edits
ReleaseEngineering/PuppetAgain: Difference between revisions
Jump to navigation
Jump to search
→The Goals
(→Action) |
|||
| Line 93: | Line 93: | ||
* 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 | ||
* 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. When a new refimage snapshot needs to be made, a 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. | ||
* OS does not imply role. Roles are defined in node declarations, by including <tt>toplevel::*</tt> classes. | * OS does not imply role. Roles are defined in node declarations, by including <tt>toplevel::*</tt> classes. | ||
* Include all necessary dependencies | * Include all necessary dependencies. Debugging dependency errors when building a new reference system is no fun. | ||
* 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 | ||