Puppet Module to manage LVM
Switch branches/tags
Nothing to show
Clone or download
Pull request Compare This branch is 317 commits behind puppetlabs:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Puppet LVM Module

Provides Logical Resource Management (LVM) features for Puppet.


This module provides four resource types (and associated providers): volume_group, logical_volume, physical_volume, and filesystem.

The basic dependency graph needed to define a working logical volume looks something like:

filesystem -> logical_volume -> volume_group -> physical_volume(s)

Here's a simple working example:

physical_volume { "/dev/hdc":
    ensure => present
volume_group { "myvg":
    ensure => present,
    physical_volumes => "/dev/hdc"
logical_volume { "mylv":
    ensure => present,
    volume_group => "myvg"
    size => "20G"
filesystem { "/dev/myvg/mylv":
    ensure => present
    fs_type => "ext3"

This simple 1 physical volume, 1 volume group, 1 logical volume case is provided as a simple volume definition, as well. The above could be shortened to be:

volume("myvg", "/dev/hdc", "mylv", "ext3", "20G")

If you need a more complex configuration, you'll need to build the resources out yourself.



Due to puppet's lack of composite keys for resources, you currently cannot define two logical_volume resources with the same name but a different volume_group.

Removing Physical Volumes

You should not remove a physical_volume from a volume_group without ensuring the physical volume is no longer in use by a logical volume (and possibly doing a data migration with the pvmove executable).

Removing a physical_volume from a volume_group resource will cause the pvreduce to be executed -- no attempt is made to ensure pvreduce does not attempt to remove a physical volume in-use.

Resizing Logical Volumes

Logical volume size can be extended, but not reduced -- this is for safety, as manual intervention is probably required for data migration, etc.