Page Comparison

...

The term "environment"

The term "environment" is heavily overloaded with respect to when discussing SIMP, Puppet, DevOps, and IT in general.  This discussion makes We attempt to make the following distinctions:

Puppet environment directory

Anchor
puppet_environment_directory puppet_environment_directory

• A single directory at $codedir/environments/<environment_name>
• r10k deploy creates one Puppet environment directory per control repository branch.
• r10k puppetfile install (using default settings) can be run at the top level a Puppet environment directory to deploy its modules from the local Puppetfile.
  
  

Puppet environment 

Anchor
puppet_environment puppet_environment

• A single conceptual Puppet environment
• Acts as a global namespace, with its own site manifest(s), modules, Hiera data (Hiera 4+), and Hiera hierarchy (Hiera 5+).
• Derives its (deployed) assets from a Puppet environment directory
• The standard Puppet sense of an "environment" when Puppet/PE operates independently from SIMP.

...

• The combined Puppet environment + SIMP Extra (Secondary + Writable) environment of the same name
• (We might need a better name for this)

Infrastructure environment

Anchor
#infrastructure_environment #infrastructure_environment

• A local site's dedicated internal infrastructure tier
• Exists independently from Puppet
• Often named something along the lines of "development," "testing, "acceptance," "staging," "production", etc.,
• In Puppet circles, this is sometimes referred to an infrastructure as an "application tier" or "permanent test environment"

Environment

Anchor
#enviroment #enviroment

• Ambiguous as ever, and could mean any of the above
• Unless context suggests otherwise, probably means "Puppet environment"

References

• (Source for https://draw.io diagrams: simp_environments.xml)