Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

maestro

MaestroDev Maestro
Project URLRSS FeedReport issues

32,184 downloads

10,302 latest version

0.1 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.

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 2.0.7 (latest)
  • 2.0.6
  • 2.0.5
  • 2.0.4
  • 2.0.3
  • 2.0.2
  • 2.0.1
  • 2.0.0
  • 1.5.3
  • 1.5.2
  • 1.5.1
  • 1.5.0
  • 1.4.7
  • 1.4.6
  • 1.4.5
  • 1.4.4
  • 1.4.3
  • 1.4.2
  • 1.4.1
  • 1.4.0
  • 1.3.20
  • 1.3.19
  • 1.3.18
  • 1.3.17
  • 1.3.16
  • 1.3.15
  • 1.3.14
  • 1.3.13
  • 1.3.12
  • 1.3.11
  • 1.3.10
  • 1.3.9
  • 1.3.8
  • 1.3.7
  • 1.3.6
  • 1.3.5
  • 1.3.4
  • 1.3.3
  • 1.3.2
  • 1.3.1
  • 1.3.0
  • 1.2.25
  • 1.2.24
  • 1.2.23
  • 1.2.22
  • 1.2.21
  • 1.2.20
  • 1.2.19
  • 1.2.18
  • 1.2.17
  • 1.2.16
  • 1.2.15
  • 1.2.14
  • 1.2.13
  • 1.2.12
  • 1.2.11
  • 1.2.10
  • 1.2.9
  • 1.2.8
  • 1.2.7
  • 1.2.6
  • 1.2.5
  • 1.2.4
  • 1.2.3
  • 1.2.2
  • 1.2.1
  • 1.2.0
  • 1.1.0
  • 1.0.2
  • 1.0.1
  • 1.0.0
released Jun 21st 2014

Start using this module

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

Add this module to your Puppetfile:

mod 'maestrodev-maestro', '2.0.7'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

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

Manually install this module globally with Puppet module tool:

puppet module install maestrodev-maestro --version 2.0.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
Tags: automation, devops, maestro, continuous, delivery

Documentation

maestrodev/maestro — version 2.0.7 Jun 21st 2014

puppet-maestro

Puppet module for installing Maestro and related software

Simple configuration

First, declare the yum repository

# Use credentials provided by MaestroDev for trial / subscription
class { 'maestro::yumrepo':
  username => $maestrodev_username,
  password => $maestrodev_password,
}

On the Maestro node, you'll need Maestro and ActiveMQ:

class { 'java': package => 'java-1.6.0-openjdk-devel' }
    
class { 'maestro::maestro':
  admin_password     => "admin1",
  master_password    => "admin1",
  db_server_password => "admin1",
  db_password        => "admin1",
}

# ActiveMQ, with Stomp connector enabled
class { 'activemq': }
class { 'activemq::stomp': }

Package['java'] -> Service['activemq']
Package['java'] -> Service['maestro']

On the agent node(s), install the agent.

class { 'java': package => 'java-1.6.0-openjdk-devel' }

class { 'maestro::agent': }
Package['java'] -> Service['maestro-agent']

(The -devel alternate packaging is only needed if you are developing Java software that will build on the agent. If not, you can use java-1.6.0-openjdk).

You can then proceed to install other software as needed on the nodes - for example Jenkins, Archiva or Sonar on the Maestro node (or standalone nodes if required), and Maven, rake, and CI agents on the agent nodes.

For example, the following installs Archiva, sharing the user database with Maestro:

$jdbc_driver_url = "${repo['url']}/postgresql/postgresql/8.4-702.jdbc3/postgresql-8.4-702.jdbc3.jar"
$archiva_jdbc = {
  url => "jdbc:postgresql://localhost/maestro",
  driver => "org.postgresql.Driver",
  username => "maestro",
  password => $maestro_db_password,
}
$repo = {
  url      => 'https://repo.maestrodev.com/archiva/repository/all/',
  username => '...',
  password => '...',
}
class { archiva:
  repo => $repo,
  version => "1.4-M1-maestro-3.4.3.1",
  port => 8082,
  archiva_jdbc => $archiva_jdbc,
  users_jdbc => $archiva_jdbc,
  jdbc_driver_url => $jdbc_driver_url,
  require => Postgres::Createdb[maestro],
}

Other modules describe how to install that particular package.

Testing

bundle install bundle exec rake spec

Development

vagrant up vagrant provision (to apply changes as tweaking)

Installing plugins

Plugins can be installed from the Maestro Web UI or be automatically installed using the maestro::plugin definition in Puppet.

For example to install some common plugins, add this to the Maestro node.

include maestro::plugins