Forge Home

vmware_puppetfact

a facter fact to convey some information about the hypervisor we are running on

612,192 downloads

611,700 latest version

1.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.2 (latest)
  • 0.2.1
released Mar 28th 2014

Start using this module

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

Add this module to your Puppetfile:

mod 'wolfspyre-vmware_puppetfact', '0.2.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add wolfspyre-vmware_puppetfact
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install wolfspyre-vmware_puppetfact --version 0.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

wolfspyre/vmware_puppetfact — version 0.2.2 Mar 28th 2014

Version 0.2.2:

  • Addition of 5.5.0 build 1369380 test and logic. Version 0.2.1.1:
  • Addition of 5.1.0 build 1065491 test Version 0.2.1:
  • Forge release
  • Attribution
  • Preparation for integration into vmwaretools module Version 0.2.0:
  • return nil on non-vmware hosts for the vmware and vmware_patchlevel facts.
  • dmidecode path is no longer hardcoded, but generated from the result of 'which dmidecode'

Version 0.1.0:

  • Major refactor of code to reside in module layout, and to provide unit tests.

This Fact is meant to allow guest VMs to know what version of ESX the hypervisor is running. This made possible from the information found here: http://virtwo.blogspot.com/2010/10/which-esx-version-am-i-running-on.html

I have tested this with the following versions

ESXi 3.5 207095 (E66C0) ESXi 4.0 171294 (EA550) ESXi 4.0u1 208167 (EA550) ESXi 4.0u2 261974 (EA550) ESXi 4.0u3 398348 (EA550) ESXi 4.0u4 504850 (EA550) ESXi 4.1 260247 (EA2E0) ESXi 4.1u2 800380 (EA2E0) ESXi 5.0 469512 (E72C0) ESXi 5.0u1 623860 (E72C0) ESXi 5.1 799733 (EA0C0) ESXi 5.1.0 1065491 (EA0C0) ESXi 5.5.0 1369380 (EA050)

ESXi 5.0u2 914586 (E72C0) support was added by https://github.com/kaistian/vmware_puppetfact

If you have access to something other than what's listed, if you wouldn't mind sending me a note containing:

  • The version/update of VMware
  • The build number
  • the output of 'dmidecode -t bios' from a linux vm inside that version I'll happily update this with that information so it can be more useful to all

NOTE: The bios is only read at power-on. A reboot will NOT update the bios information. If you notice an incorrect bios string, try powering off the VM completely and powering it back on. This will reload the bios, and you should have the proper address and release date.

Thanks to: Adrien Thiebo Stefan Heijmans Eric Shamow Mike Arnold Kai Stian Olstad Eric Sakowski Søren Andreas Bodekær Kröger