Skip to content

esalberg/puppet-vmwaretools

Repository files navigation

puppet-vmwaretools

Build Status

Wanted: User Reports & Testimonials

I'd like to put together a small set of reports and testimonials from Puppet users who have implemented this module within their infrastructure.

If you'd like to get involved, please reach out via email [email protected], Twitter @craigwatson1987 or Google+.

Table of Contents

  1. Overview - What is the puppet-vmwaretools module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with puppet-vmwaretools
  4. Usage - Configuration options and additional functionality
  5. Reference - An under-the-hood peek at what the module is doing
  6. Limitations - OS compatibility, etc.
  7. Development - Guide for contributing to the module

Overview

This module manages the installation and upgrade of VMware Tools via the source code tarballs distributed by VMware.

Module Description

This module is designed to replace both the OSP packages provided by VMware's repositories and also the open-vm-tools package. The module is O/S independent (tested on Ubuntu and Red Hat systems).

The tarballs are transferred to the target by either HTTP download or Puppet filebucket (the default mechanism), and then uncompressed and installed via the archive's Perl installation script.

Upgrading of currently installed VMware Tools packages is also supported - the module obtains the currently-installed VMware Tools version via a custom fact, and only deploys the tarball if a version mismatch occurs or if VMware Tools is not installed on the target system.

Setup

What puppet-vmwaretools affects

  • Compares installed version with the configured version via the vmwaretools fact
  • Transfer the VMware Tools archive to the target agent (via Puppet or HTTP)
  • Untar the archive and run vmware-install-tools.pl (warning: this installer is run with the -d flag to accept all default answers).
  • Removes the open-vm-tools package.

Setup Requirements

  • Perl must be installed on the target systems in order to run the VMware Tools installer - installation of Perl is not handled by the module.
  • Pluginsync must be enabled, due to the vmwaretools_version custom fact distributed with this module. If the module cannot access the fact, the Puppet run will fail.
  • As of version 1.0.0, the module requires the PuppetLabs stdlib module module to be available within your Puppet code.

Beginning with puppet-vmwaretools

To accept default class parameters:

include vmwaretools

Usage

The source distribution mechanism can be customised by declaring the module with archive_url and archive_md5 parameters (default is to use Puppet filebuckets).

To specify a non-default version, working directory and HTTP URL (other variables can be viewed and/or modified in manifests/init.pp):

class { 'vmwaretools':
  version     => '8.6.5-621624',
  working_dir => '/tmp/vmwaretools',
  archive_url => 'http://server.local/my/dir',
  archive_md5 => '9df56c317ecf466f954d91f6c5ce8a6f',
}

Reference

Facts

vmwaretools_version

  • Detects any existing VMware Tools installations and, if found, reports the installed version.

esx_version

Classes

vmaretools::config

  • Deploys the working directory in which the module downloads and extracts the archive, and runs the Perl installer.

vmwaretools::install::exec

  • Declares all exec commands run by the module.

vmwaretools::install::package

  • Handles installing the required tools to compile and install the archive, as well as purging OSP and open-source VMware Tools packages.
  • NOTE: Due to bugs in Puppet's yum provider, the OSP/open-source packages are only marked as absent, not purged.

vmwaretools::install::archive

  • Handles the archive distribution (either places a download script or the archive).

vmwaretools::params

  • O/S-specific and module configuration (e.g. paths to binaries and a boolean variable to control file deployment)

vmwaretools::config_tools

  • Executes vmware-config-tools.pl -d if the vmci.ko module doesn't exist for the running kernel

vmwaretools::timesync

  • Handles time synchronisation between the virtual machine and host

Limitations

Supported Operating Systems

  • Ubuntu - 12.04 LTS (Precise) and 10.04 LTS (Lucid) tested
  • Red Hat family - RHEL 5 and 6 tested
  • Debian family - written but untested, reports appreciated

Unsupported Operating Systems

Development

About

Puppet module for non-OSP VMware Tools Installation

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Puppet 62.2%
  • Ruby 33.0%
  • Shell 4.8%