Forge Home

hbase

A module for managing HBase and the HBase REST API

11,635 downloads

9,546 latest version

3.0 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

  • 0.1.0 (latest)
  • 0.0.5
  • 0.0.4
  • 0.0.3
  • 0.0.2
  • 0.0.1
released Jan 23rd 2015
This version is compatible with:
  • RedHat

Start using this module

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

Add this module to your Puppetfile:

mod 'myoung34-hbase', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add myoung34-hbase
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install myoung34-hbase --version 0.1.0

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

myoung34/hbase — version 0.1.0 Jan 23rd 2015

puppet-hbase

Build Status Coverage Status Bitdeli Badge

Puppet Module For HBase

About

HBase Apache HBase is the Hadoop database, a distributed, scalable, big data store. This module is aimed at CentOS only (untested on RHEL). This module starts the HBase master and REST API with built-in zookeeper.

Supported Versions (tested)

OS

  • CentOS 6
    • hbase-0.98.0.2.1.3.0

Quick Start

    include hbase

    class { 'hbase':
      rest_port => '8080' # 8000 is default
    }

Hiera

hbase::rest_port: '8080'

Testing

  • Run the default tests (puppet + lint)

      bundle install 
      bundle exec rake
    
  • Run the beaker acceptance tests

      $ bundle exec rake acceptance
    

Submitting pull requests

I use the the gitflow model.

  • Features should be created with a 'feature' prefix, such as 'feature/add-something'.
  • Bugs should be created in a branch with a 'bugfix' prefix, such as 'bugfix/issue-4' or 'bugfix/timing-issue'.

Verify tests pass, then submit a pull request and make sure your branch has been rebased against my default branch (master).