Forge Home


A custom fact module that maps the output of 'lsmpio -q' for disk<->LUN name mappings


34 latest version

5.0 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.1.0 (latest)
released Jul 9th 2024
This version is compatible with:
  • Puppet Enterprise 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2021.7.x
  • Puppet >= 7.24 < 9.0.0

Start using this module

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

Add this module to your Puppetfile:

mod 'cryssoft-aix_mpio_facts', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add cryssoft-aix_mpio_facts
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install cryssoft-aix_mpio_facts --version 0.1.0

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.



cryssoft/aix_mpio_facts — version 0.1.0 Jul 9th 2024


Table of Contents

  1. Description
  2. Setup - The basics of getting started with aix_mpio_facts
  3. Usage - Configuration options and additional functionality
  4. Limitations - OS compatibility, etc.
  5. Development - Guide for contributing to the module


The cryssoft-aix_mpio_facts module provides a custom fact that maps the output of the 'lsmpio -q' into a hash with two parts that allow easy mapping of disk device to LUN name or vice versa. This is most useful when 'lsmpio -q' shows values that can be predicted or standardized.


Put the module in place in your Puppet master server as usual. AIX-based systems will start populating the $::facts['aix_mpio'] hash with their next run, and you can start referencing those facts in your classes.

What aix_mpio_facts affects OPTIONAL

At this time, the cryssoft-aix_mpio_facts module ONLY supplies custom facts. It does not change anything and should have no side-effects.

Setup Requirements OPTIONAL

As a custom facts module, I believe pluginsync must be enabled for this to work.

Beginning with aix_mpio_facts

If you're using Puppet Enterprise, the new fact(s) will show up in the PE console for each AIX-based node under management. If you're not using Puppet Enterprise, you'll need to use a different approach to checking for their existence and values.


As noted, cryssoft-aix_mpio_facts is only providing custom facts. Once the module and its Ruby payload are distributed to your AIX-based nodes, those facts will be available in your classes.


$::facts['aix_mpio'] is the top of a hash. That's it.


This module has been tested and worked on AIX 7.2 and 7.3 systems and VIOS 3.1 and 4.1 systems.


In the Development section, tell other users the ground rules for contributing to your project and how they should submit their work.

Release Notes/Contributors/Etc. Optional

Starting this with a new version for the first up-load.