Forge Home


This module provides native types and providers to manage LSI MegaRAID devices


5,685 latest version

4.3 quality score

Version information

  • 1.1.1 (latest)
  • 1.1.0
  • 1.0.6
  • 1.0.5
  • 1.0.4
  • 1.0.3
  • 1.0.2
  • 1.0.1
  • 1.0.0
  • 0.0.3
  • 0.0.2
  • 0.0.1 (deleted)
released Jun 9th 2017
This version is compatible with:
  • Puppet Enterprise 2017.2.x, 2016.4.x
  • Puppet >= 4.10.0 < 5.0.0
  • , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'm4ce-megaraid', '1.1.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add m4ce-megaraid
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install m4ce-megaraid --version 1.1.1

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.



m4ce/megaraid — version 1.1.1 Jun 9th 2017

Puppet types and providers for LSI MegaRAID

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 the megaraid module
  4. Reference - Types reference and additional functionalities
  5. Hiera integration
  6. Contact


This module implements native types and providers to manage some aspects of LSI MegaRAID devices.

Module Description

The megaraid module allows to automate the configuration of LSI MegaRAID devices. Currently, it only supports managing virtual disks.


The module requires the storcli package in order to manage MegaRAID volumes. An RPM version is available for download here.

A custom fact named 'has_megaraid' defines whether your system is equipped with one or more LSI MegaRAID devices.

You can use that fact to optionally include the megaraid class in your manifests as shown below:

if $::has_megaraid {
  include megaraid




megaraid_vd manages virtual disks using the StorCLI utility

megaraid_vd {"data":
  controller => 0,
  raid_type => 1,
  drives => "1,2" # If the Enclosure ID is not given, the first one available will be picked (this will generate a warning message though)
name (required)

Name to describe the VD


Virtual disk name, defaults to name

ensure (required)

Whether the resource is present or not. Valid values are 'present', 'absent'. Defaults to 'present'.

controller (required)

Controller Index, must be an Integer

raid_type (required)

RAID type. Valid values are: 0, 1, 5, 6, 10, 50, 60.


Logical drive cache policy. Valid values are: 'direct', 'cached'.


Write policy. Valid values are: 'wb', 'wt'.


Access policy. Values values are: 'rw', 'ro', 'blocked', 'rmvblkd'.


Read policy. Values values are: 'ra', 'nora'.

drives (required)

Physical drives to use. Valid syntax is [e:]s|[e:]s-x|[e:]s-x,y,[e:]s-x,y,z


Physical drives to be used as spares. Valid syntax is [e:]s|[e:]s-x|[e:]s-x,y,[e:]s-x,y,z


Number of physical drives per array. Must be an Integer between 0..15.


Strip size. Valid values are: 8, 16, 32, 64, 128, 256, 512, 1024.


Enables or disables PD cache. Valid values are: on, off, default.


Creates security-enabled drives. Must be a Boolean.


Enables protection information. Must be a Boolean.


Power-saving policy. Valid values are: automatic, none, max, maxnocache.


Creates the VD in the adjacent free slot next to the specified VD.


Forces a security-capable physical drive to be added to a drive group without security. Must be a Boolean, default is false.

Hiera integration

You can optionally define your virtual disks in Hiera using the megaraid::virtual_disks class parameter.

    controller: 0
    raid_type: 1
    drives: 1,2
    iopolicy: "direct"
    writepolicy: "wb"
    readpolicy: "ra"
    controller: 0
    raid_type: 10
    drives: 3-6
    strip: 512


Matteo Cerutti -