Changes between Version 10 and Version 11 of how-to/puppet/layout


Ignore:
Timestamp:
May 4, 2013, 9:20:05 PM (6 years ago)
Author:
Daniel Kahn Gillmor
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • how-to/puppet/layout

    v10 v11  
    1313== Layout ==
    1414
    15 Below is the layout of our [https://git.mayfirst.org/?p=mfpl/puppet.git;a=summary git repository].
     15Below is the layout of our [source:puppet puppet git repository].
    1616
    17  * helper holds code for running operations on our servers from the command line using the freepuppet command. For a list of options run:
     17 [source:puppet/helper helper/]::
     18  holds code for running operations on our servers from the command line using the `freepuppet` command. For a list of options run:
    1819{{{
    1920helper/freepuppet-helper -l
    2021}}}
    21  * manifests: this is where information about each MFPL server is stored, plus some general information specific to our servers
    22   * site.pp: this is the file that boostraps all other files
    23   * globals.pp: global variables specific to May First/People Link, used throughout
    24   * modules.pp: one line to import every puppet module that we use. We only use one module: mayfirst
    25   * nodes: this directory contains the files for each server in our network
    26    * production: one file for every production server in our network
    27    * dev:  one file for every test/dev server
    28  * modules: modules are abstracted collections of manifests, templates and files. All of our puppet code is in the mayfirst module.
     22 [source:puppet/manifests manifests/]::
     23   this is where information about each MFPL server is stored, plus some general information specific to our servers
     24  * [source:puppet/manifests/site.pp site.pp]: this is the file that boostraps all other files
     25  * [source:puppet/manifests/globals.pp globals.pp]: global variables specific to May First/People Link, used throughout
     26  * [source:puppet/manifests/modules.pp modules.pp]: one line to import every puppet module that we use. We only use one module: mayfirst
     27  * [source:puppet/manifests/nodes nodes/]: this directory contains the files for each server in our network
     28   * [source:puppet/manifests/nodes/production production/]: one file for every production server in our network
     29   * [source:puppet/manifests/nodes/dev dev/]:  one file for every test/dev server
     30 [source:puppet/modules modules/]::
     31   modules are abstracted collections of manifests, templates and files. All of our puppet code is in the mayfirst module.
    2932
    3033= Puppet Resources =
     
    4548}}}
    4649
    47 This file resource ensures that a file located at /etc/aliases on the target server will be created. The content of the file will be based on the template located in the puppet repository in modules/mayfirst/postfix/aliases.erb (this template contains variables that will be dynamically filled in).
     50This file resource ensures that a file located at /etc/aliases on the target server will be created. The content of the file will be based on [source:puppet/modules/mayfirst/postfix/aliases.erb its template] (this template contains variables that will be dynamically filled in).
    4851
    4952== execs ==
     
    148151}}}
    149152
    150 $namesake and $purpose are not used by puppet - they are there for human readability.
     153`$namesake` and `$purpose` are not used by puppet - they are there for human readability.
    151154
    152155= Variable Scoping =
    153156
    154 Global variables are defined in manifests/globals.pp and have an mfpl_ prefix. They are accessible anywhere in the code, provided you use the double colon syntax: $::, e.g. $::mfpl_admin_user_ids.
     157Global variables are defined in [source:puppet/manifests/globals.pp] and have an `mfpl_` prefix. They are accessible anywhere in the code, provided you use the double colon syntax: `$::`, e.g. `$::mfpl_admin_user_ids`.
    155158
    156159All other variables should be properly scoped.