Forge Home

mdadm

Manages the `mdadm` util for Linux software RAID arrays

14,804 downloads

14,804 latest version

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

Version information

  • 0.1.0 (latest)
released May 21st 2014

Start using this module

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

Add this module to your Puppetfile:

mod 'jhoblitt-mdadm', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add jhoblitt-mdadm
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install jhoblitt-mdadm --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

jhoblitt/mdadm — version 0.1.0 May 21st 2014

Puppet mdadm Module

Build Status

Table of Contents

  1. Overview
  2. Description
  3. Usage
  4. Limitations
  5. Versioning
  6. Support
  7. See Also

Overview

Manages the mdadm util for Linux software RAID arrays

Description

This module installs the mdadm package for the management of Linux Software RAID arrays, and provides limited configuration support. Specifically, this module does not presently provide any support for the creation, modification, or removal of md arrays. Management is limited to configuring monitoring of pre-existing md arrays, and array health checks.

Usage

Examples

Simple

include ::mdadm

Set mdmonitor email address

class { '::mdadm':
  config_file_options => { 'mailaddr' => 'root' },
}

Classes

mdadm

# defaults
class { '::mdadm':
  config_file_manage  => true,
  config_file_options => {},
  force_service       => false,
  service_ensure      => 'running',
  service_enable      => true,
  raid_check_manage   => true
  raid_check_options  => {},
}
config_file_manage

Bool defaults to true

Enables/disables management of the mdadm.conf configuration file.

config_file_options

Hash defaults to '{}'

Keyword/value pairs to be set in the mdadm.conf configuration file. Currently, mailaddr is the only supported key. Example:

  config_file_options => { 'mailaddr' => 'root' },
force_service

Bool defaults to false

By default, the mdadm class will not attempt to start the mdmonitor service unless the $::mdadm_arrays fact lists md arrays. If this parameter is set to true the class will always attempt to start the mdmonitor service.

service_ensure

String defaults to 'running'

Sets the state of the mdmonitor service. Valid strings are: 'running', 'stopped'

service_enable

Bool defaults to 'true'

Enables/disables the mdmonitor service on boot.

raid_check_manage

Bool defaults to true

Enables/disables management of the EL specific raid-check cron task.

raid_check_options

Hash defaults to '{}'

Keyword/value pairs to be set in the /etc/sysconfig/raid-check configuration file. Example:

  raid_check_options => {
    'ENABLED'       => 'yes',
    'CHECK'         => 'check',
    'NICE'          => 'low',
    'CHECK_DEVS'    => '/dev/md0 /dev/md1',
    'REPAIR_DEVS'   => '/dev/md0',
    'SKIP_DEVS'     => '/dev/md1',
    'MAXCONCURRENT' => '2',
  },

Facts

mdadm

Path to the mdadm executable. Example:

/sbin/mdadm

mdadmversion

Version string of the mdadm executable. Example:

v3.2.3

mdadm_arrays

A listing of /dev/<foo> md devices. Example:

/dev/md0,/dev/md1

Limitations

Tested Platforms

  • el6.x
  • el5.x

Versioning

This module is versioned according to the Semantic Versioning 2.0.0 specification.

Support

Please log tickets and issues at github

See Also