canmove, Confirmed users
1,394
edits
| Line 143: | Line 143: | ||
== Puppetmasters == | == Puppetmasters == | ||
PuppetAgain masters are managed by PuppetAgain. Each organization can have 1 or more masters, arranged in a cluster. There is one "distinguished master" in the cluster. This master is distinguished only for purposes of simplifying synchronization -- the cluster will continue to operate indefinitely without the distinguished master, although master-master communication (secrets and CRLs) will not work. | PuppetAgain masters are managed by PuppetAgain. Each organization can have 1 or more masters, arranged in a cluster (with one cluster per organization). There is one "distinguished master" in the cluster. This master is distinguished only for purposes of simplifying synchronization -- the cluster will continue to operate indefinitely without the distinguished master, although 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. | See the following for more details, noting that most of this is not required for an external PuppetAgain implementation. | ||
| Line 174: | Line 174: | ||
See [[ReleaseEngineering/PuppetAgain/Packages]] for information about proper handling of packages in PuppetAgain. | See [[ReleaseEngineering/PuppetAgain/Packages]] for information about proper handling of packages in PuppetAgain. | ||
== | == Aspects == | ||
Taking a page from [http://en.wikipedia.org/wiki/Aspect-oriented_programming Aspect Oriented Programming], PuppetAgain implements Aspect Oriented Puppet. Aspects cross-cut the concerns represented by the toplevel hierarchy. For example, whether a host is a staging host, whether it is loaned out, etc. See [[ReleaseEngineering/PuppetAgain/Aspects] for details. | |||
== Source Code == | |||
The manifests are at http://hg.mozilla.org/build/puppet. | |||
= History = | = History = | ||