Changes

Jump to: navigation, search

ReleaseEngineering/PuppetAgain

422 bytes added, 16:58, 9 May 2013
System Description
== Puppetmasters ==
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 [[ReleaseEngineering/PuppetAgain/Packages]] for information about proper handling of packages in PuppetAgain.
== Manifests Aspects ==
Manifests 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 =
Canmove, confirm
1,394
edits

Navigation menu