Forge Home

Modules

Resources

PuppetEcosystemPuppet CommunityUpdates

lizardfs

Install and Configure LizardFS
Project URLRSS FeedReport issues

9,582 downloads

6,851 latest version

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

  • 1.2.2 (latest)
  • 1.2.1
  • 1.2.0
  • 1.1.0
  • 1.0.8
  • 1.0.7
  • 1.0.6
  • 1.0.5
  • 1.0.4
  • 1.0.3
  • 1.0.2
  • 1.0.1
  • 1.0.0
released Mar 18th 2017
This version is compatible with:
  • Puppet Enterprise 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 3.0.0 < 5.0.0
  • , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'Asher256-lizardfs', '1.2.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add Asher256-lizardfs
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install Asher256-lizardfs --version 1.2.2

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

Asher256/lizardfs — version 1.2.2 Mar 18th 2017

puppet-lizardfs

Table of Contents

  1. Overview
  2. Example
  3. High-Availability
  4. Requirements
  5. Contribute

Overview

The puppet-lizardfs module lets you use Puppet to install and configure LizardFS automatically.

LizardFS is an open source distributed file system, highly available, scalable and ready to use.

You can configure with puppet-lizardfs:

  • The LizardFS master (ready for High-availability with tools like keepalived or Pacemaker. Check out the explanation below)
  • The LizardFS chunkserver
  • The LizardFS metalogger
  • The LizardFS client and mount points

Puppet dependencies (Puppet modules):

  • stdlib

Example

To configure the LizardFS master:

class {'lizardfs::master':
  ensure              => 'present',
  first_personality   => 'MASTER',
  exports             => ['*    /    ro'],
}

To configure the chunkserver:

host { 'mfsmaster':
  ip => 'x.x.x.x',
}

->
class {'lizardfs::chunkserver':
  ensure => present,
}

To mount a LizardFS mount point:

lizardfs::mount {'/mnt/':
  lizardfs_subfolder => '/',
  lizardfs_master    => 'x.x.x.x',   # the IP / host of the LizardFS Master
}

To configure the metalogger:

# FYI: the host "mfsmaster" need to be set, like the chunkserver example below
class {'lizardfs::metalogger':
  ensure => present,
}

High-Availability

The Puppet module "puppet-lizardfs" is ready for the High-Availability (BETA).

You can try the BETA version of the keepalived class lizardfs::ha::keepalived starting by now. Example:

class {'lizardfs::master':
  ensure              => 'present',
  first_personality   => 'MASTER',
  exports             => ['*    /    ro'],
}

class {'lizardfs::ha::keepalived':
  interface          => "eth0",
  virtual_router_id  => "246",
  auth_pass          => "ThePassword",
  email_enabled      => true,
  email_from         => "from-email@gmail.com",
  smtp_server        => "smtp.domain.com",
  email_to           => "youremail@gameloft.com",
  virtual_ip         => ["10.10.10.2/24 dev eth0 label eth0:mfsmaster"],
  lvs_id             => "LIZARDFS_$${:fqdn}",
}

How the lizardfs::ha::keepalived works? First, let me explain how the "PERSONALITY" is managed by puppet-lizardfs:

  • The first time the 'PERSONALITY' is set in 'mfsmaster.cfg' (with the variable lizardfs::master::first_personality), the variable 'PERSONALITY' is not overwritten by Puppet anymore.
  • The fact that "PERSONALITY" is not overwritten by Puppet gives you the possibility to modify the personality with a tool like keepalived, generate mfsmaster.cfg with the new personality and restart the LizardFS master. Your high-availability scripts can change the personality with this script created by puppet-lizardfs /etc/lizardfs/generate-mfsmaster-cfg.sh

The class lizardfs::ha::keepalived (BETA) will switch the personality from SHADOW to MASTER with the failover script. The failover script.

(The Pacemaker support is coming. Check the ALPHA version in misc/alpha/pacemaker.pp if you want to test it or improve it).

Requirements

  • Operating system: Debian, Ubuntu, CentOS, RedHat

Contribute

This Puppet module is an open project, and community contributions are essential for keeping it great. I can't access the huge number of platforms and myriad hardware, software, and deployment configurations that Puppet is intended to serve. I encourage you to contribute. Send me your pull requests on Github!