ebs

Attach and partition EBS volumes

Project URL RSS Feed Report issues

Module Stats

14,474 downloads

7,502 latest version

2.8 quality score

Version information

released Oct 5th 2015

Start using this module

Installation method

Add this module to your Puppetfile:

mod 'ignis-ebs', '0.1.0'

Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add ignis-ebs

Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install ignis-ebs --version 0.1.0

Documentation

ignis/ebs — version 0.1.0 Oct 5th 2015

ecryptfs

Overview
Usage - Configuration options and additional functionality
Limitations - OS compatibility, etc.

Overview

This module provides allows to manage EBS volumes (attach, format, mount). Volumes should be created outside of puppet, for example, using CloudFormation. The module performs a lookup searching for a volume in question by a 'name' tag's value.

All the interactions with AWS API are performed with aws commandline utilities.

Usage

Be sure to create a volume beforehand. E.g., here is a snippet for CloudFormation:

"JenkinsMasterStorageVolume": {
  "Type": "AWS::EC2::Volume",
  "Properties": {
    "Encrypted": true,
    "AvailabilityZone": "eu-west-1a",
    "Size": 100,
    "Tags": [
      {
        "Key": "name",
        "Value": "jenkins"
      }
    ]
  }
},

Or awscli:

aws ec2 create-volume --availability-zone $${AWS_DEFAULT_REGION}a \
  --size 1 --encrypted --volume-type standard \
  --query '{id:VolumeId}' \
  | grep '"id"' | awk '{print $$2}' \
  | tr -d '"' | perl -pe chomp > .volume_id
aws ec2 create-tags --resources `cat .volume_id` \
  --tags Key=name,Value=jenkins

And then in your puppet code you can create resources like this:

ebs::volume { 'jenkins':             # so we look for an EBS volume that has name:jenkins tag set
  device         => '/dev/sdj',      # /dev/sdb by default
  format         => 'ext3',          # ext3 by default
  format_options => '-L jenkins',    # this will be passed to mkfs.ext3 AS IS, string format
  mount_dir      => '/mnt/jenkins',  # /mnt by default
  mount_options  => 'nodev, noatime' # single string, fstab format, 'noatime' by default
}

mount_dir directory will be created if it doesn't exist (so manage it outside of this module to ensure custom owner/group/mode parameters).

Limitations

This module was tested on CentOS 6.x so far. For the AWS API authorization to work, you have to assign a proper IAM role to an ec2 instance you're running this code on. Example policy (tune Resource parameter to your liking):


    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1444046341000",
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeVolumes",
                "ec2:AttachVolume"
            ],
            "Resource": [
                "*"
            ]
        }
    ]
}

Types in this module release

file_line

Ensures that a given line is contained within a file. The implementation matches the full line, including whitespace at the beginning and end. If the line is not contained in the given file, Puppet will append the line to the end of the file to ensure the desired state. Multiple resources may be declared to manage multiple lines in the same file.

Example:

    file_line { 'sudo_rule':
      path => '/etc/sudoers',
      line => '%sudo ALL=(ALL) ALL',
    }

    file_line { 'sudo_rule_nopw':
      path => '/etc/sudoers',
      line => '%sudonopw ALL=(ALL) NOPASSWD: ALL',
    }

In this example, Puppet will ensure both of the specified lines are
contained in the file /etc/sudoers.

Match Example:

    file_line { 'bashrc_proxy':
      ensure => present,
      path   => '/etc/bashrc',
      line   => 'export HTTP_PROXY=http://squid.puppetlabs.vm:3128',
      match  => '^export HTTP_PROXY=',
    }

In this code example match will look for a line beginning with export 
followed by HTTP_PROXY and replace it with the value in line.

Match Example With `ensure => absent`:

    file_line { 'bashrc_proxy':
      ensure            => absent,
      path              => '/etc/bashrc',
      line              => 'export HTTP_PROXY=http://squid.puppetlabs.vm:3128',
      match             => '^export HTTP_PROXY=',
      match_for_absence => true,
    }

In this code example match will look for a line beginning with export
followed by HTTP_PROXY and delete it.  If multiple lines match, an
error will be raised unless the `multiple => true` parameter is set.

**Autorequires:** If Puppet is managing the file that will contain the line
being managed, the file_line resource will autorequire that file.

Parameters
after	An optional value used to specify the line after which we will add any new lines. (Existing lines are added in place)
ensure
line	The line to be appended to the file or used to replace matches found by the match attribute.
match	An optional ruby regular expression to run against existing lines in the file. If a match is found, we replace that line rather than adding a new line. A regex comparisson is performed against the line value and if it does not match an exception will be raised.
match_for_absence	An optional value to determine if match should be applied when ensure => absent. If set to true and match is set, the line that matches match will be deleted. If set to false (the default), match is ignored when ensure => absent.
multiple	An optional value to determine if match can change multiple lines. If set to false, an exception will be raised if more than one line matches
name	An arbitrary name used as the identity of the resource.
path	The file Puppet will ensure contains the line specified by the line parameter.
provider
replace	If true, replace line that matches. If false, do not write line if a match is found

Providers
ruby
ruby

anchor

A simple resource type intended to be used as an anchor in a composite class.

In Puppet 2.6, when a class declares another class, the resources in the interior class are not contained by the exterior class. This interacts badly with the pattern of composing complex modules from smaller classes, as it makes it impossible for end users to specify order relationships between the exterior class and other modules.

The anchor type lets you work around this. By sandwiching any interior classes between two no-op resources that are contained by the exterior class, you can ensure that all resources in the module are contained.

  class ntp {
    # These classes will have the correct order relationship with each
    # other. However, without anchors, they won't have any order
    # relationship to Class['ntp'].
    class { 'ntp::package': }
    -> class { 'ntp::config': }
    -> class { 'ntp::service': }

    # These two resources "anchor" the composed classes within the ntp
    # class.
    anchor { 'ntp::begin': } -> Class['ntp::package']
    Class['ntp::service']    -> anchor { 'ntp::end': }
  }

This allows the end user of the ntp module to establish require and before relationships with Class['ntp']:

  class { 'ntp': } -> class { 'mcollective': }
  class { 'mcollective': } -> class { 'ntp': }

Parameters
name	The name of the anchor resource.

Modules

Discover

Contribute

Resources

About Forge

Getting Started

ebs

Scheduled for Deprecation