Forge Home

maestro_demo

MaestroDev Maestro Demo Compositions and Projects

16,960 downloads

9,647 latest version

1.8 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.1.7 (latest)
  • 1.1.6
  • 1.1.5
  • 1.1.3
  • 1.1.2
  • 1.1.1
  • 1.1.0
  • 1.0.24
  • 1.0.23
  • 1.0.22
  • 1.0.21
  • 1.0.20
  • 1.0.19
  • 1.0.18
  • 1.0.17
  • 1.0.16
  • 1.0.15
  • 1.0.14
  • 1.0.13
  • 1.0.12
  • 1.0.11
  • 1.0.10
  • 1.0.9
  • 1.0.8
  • 1.0.7
  • 1.0.6
  • 1.0.5
  • 1.0.4
  • 1.0.3
  • 1.0.2
  • 1.0.1
  • 1.0.0
released May 12th 2014

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'maestrodev-maestro_demo', '1.1.7'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add maestrodev-maestro_demo
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install maestrodev-maestro_demo --version 1.1.7

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

maestrodev/maestro_demo — version 1.1.7 May 12th 2014

puppet-maestro-demo

Demos are processed in the following order:

  1. SOURCE-TYPES
  2. SOURCES
  3. COMPOSITIONS

Layout

manifests -+- demo -+- source_type -+- base.pp               # Core stuff
           |        |               |
           |        |               +- generic.pp            # A generic (name only) source-type
           |        |               |
           |        |               +- <whatever.pp>         # Custom source-type that is more than just a name
           |        |
           |        +- source ------+- base.pp               # Core stuff
           |        |               |
           |        |               +- generic.pp            # A generic (name only) source
           |        |               |
           |        |               +- <whatever.pp>         # Custom source that is more than just a name
           |        |
           |        +- composition -+- base.pp               # Core stuff
           |                        |
           |                        +- generic.pp            # A generic (name only) composition
           |                        |
           |                        +- <whatever.pp>         # Custom composition that is more than just a name
           |
           |
templates -+- demo -+- source_type -+- <whatever.json.erb>   # The source_type template
           |        |
           |        +- source ------+- <whatever.json.erb>   # The source template
           |        |
           |        +- composition -+- <whatever.json.erb>   # The composition template
           |
           |
files --- -+- demo -+- source_type -+- <whatever>            # Any support files required by custom source_type(s)
                    |
                    +- source ------+- <whatever>            # Any support files requires by custom source(s)
                    |
                    +- composition -+- <whatever>            # Any support files requires by custom composition(s)

Each demo can have its own puppet class, so individual demos have better control over their own dependencies. Many demos may not require their own puppet class, so a "generic" one has been made available. It takes only a name parameter, and uses that to locate the appropriate "${name}.json.erb" file in the respective template directory.

Disabling a demo

When calling the 'base.pp' for a source_type, source, or composition, a parameter "enabled" may be set to false. This will cause the demo to NOT be installed. Alternatively, you could just comment out the line :)

Non-working demos

A Number of demos may not work out of the box. This is expected. Some will require additional manual configuration (i.e. login credentials, hostnames, etc), and others may only be present to show that a given feature is available, but is not supported in the limited demonstration environment available. Full demonstrations are available by using the contact link on http://www.maestrodev.com