Puppet module to manage Apache Ambari

North Development



5,511 latest version

4.5 quality score

Version information

  • 0.2.0 (latest)
  • 0.1.3
  • 0.1.2
  • 0.1.1
released Aug 26th 2016
This version is compatible with:
  • RedHat

Start using this module


unibet/ambari — version 0.2.0 Aug 26th 2016


Build Status Puppet Forge Puppet Forge

Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Setup - The basics of getting started with ambari
  4. Usage - Configuration options and additional functionality
  5. Reference - An under-the-hood peek at what the module is doing and how
  6. Limitations - OS compatibility, etc.
  7. Development - Guide for contributing to the module


From the Apache Ambari docs: "The Apache Ambari project is aimed at making Hadoop management simpler by developing software for provisioning, managing, and monitoring Apache Hadoop clusters. Ambari provides an intuitive, easy-to-use Hadoop management web UI backed by its RESTful APIs."

This module aims to manage the infrastructure bits surrounding Ambari, such as package installation, service state management.

Note this module is currently work in progress, however any breaking changes will only be introduced in new minor versions.

Module Description

Current scope of this module is to provide package installation, service state management and support for running the unattended default server bootstrap.


What ambari affects

  • Installs ambari-server
  • Optionally manages package repository
  • Runs unattended ambari-server setup
  • Manages the ambari-server service

Setup Requirements

No extra setup requirements needed.


Use class ambari::server to manage the Ambari server installation. Version to install is set in the ambari class in case we expand the possibility to manage ambari agents


Class: ambari::server

class { '::ambari::server':
  use_repo   => true,
  db_backend => 'mysql'


Tested on EL6


Fork it, create feature branch, make sure your changes pass lint, compilation and unit tests, then create pull request.

Code / catalog testing:

bundle install
bundle exec rake lint
bundle exec rake validate
bundle exec rake spec

Integration testing:

bundle install
bundle exec kitchen test

Release Notes