Forge Home


The bmclib is a module that automates deployment of ipmi devices and provides other useful types


7,708 latest version

4.6 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.2.1 (latest)
  • 0.2.0
  • 0.1.5
  • 0.1.4
  • 0.1.3
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Feb 2nd 2016
This version is compatible with:
  • , , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'logicminds-bmclib', '0.2.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add logicminds-bmclib
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install logicminds-bmclib --version 0.2.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.



logicminds/bmclib — version 0.2.1 Feb 2nd 2016

module name

Module development setup

Install all the require gems to run test code

bundle install  (only need to do once)

Running Tests

Unit tests

This type of testing is fast and should be the first thing you do before comming your code. Mistakes can be found in a matter of seconds vs minutes/hours. You can test your logic in a unit test. The downside is you need to learn how to write unit tests which can take some initial time getting used to.

bundle exec rake spec

Integration Testing

This type of testing is somewhat manual and requires the use of vagrant and a test vm that is controlled by vagrant. You can find the list of available test vms by running vagrant status in the root of the module directory. There is at lot of magic happening in the vagrantfile that makes this easy. Windows support with this module has not been added yet.

$ vagrant status
Current machine states:

win2012r2                 not created (vmware_fusion)
win2008r2                 not created (vmware_fusion)
centos6                   running (vmware_fusion)

To run a test first you need to define the test code located in module_root/tests directory. This code is nothing more than a bunch of puppet code that uses your manifest code. You will be using puppet apply to run this code on the vm. Have a look inside the tests directory for examples.

Example test file

include profiles::default_linux
    ensure => file,
    content => 'Hello World'

There are a few ways to run the test code against a test vm, both of which have the same outcome.

bundle exec rake spec_prep
VAGRANT_MANIFEST=linux.pp vagrant provision centos6

or use the rake command which bundles the two commands together

bundle exec rake "vagrant_up[linux.pp,centos6]"

Acceptance Tests

Acceptance testing is sorta like combining unit testing and integration testing where it tests the code on real systems automatically across a wide range of operating systems. This is an advanced topic, so yu will want to master unit and integration testing first before writing acceptance tests.

bundle exec rake beaker

CI config doc