Forge Home

vcsa

VMware vCSA puppet module

12,473 downloads

6,586 latest version

2.3 quality score

Version information

  • 0.7.0 (latest)
  • 0.3.0
  • 0.0.1
released Sep 15th 2016

Start using this module

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

Add this module to your Puppetfile:

mod 'vmware-vcsa', '0.7.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add vmware-vcsa
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install vmware-vcsa --version 0.7.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.

Download

Documentation

vmware/vcsa — version 0.7.0 Sep 15th 2016

VMware vCSA module

Build Status

This module initializes and manages VMware vCenter Server Appliance (vCSA).

Description

VMware vCenter Server Appliance does not include or support puppet agent. The module manages vCSA through an intermediate host running puppet. The management host connects to vCSA via ssh to perform the initialization and configuration:

+------------+         +-------+
|            |   ssh   | vCSA  |
|   Puppet   | +-----> +-------+
| Management |   |
|    Host    |   |     +-------+
|            |    ---> | vCSA  |
+------------+         +-------+

A single management host can support any number of vCSA as long it has connectivity to the appliances.

Installation

$ puppet module install vmware/vcsa

Usage

Deploy vCSA image to ESX (via ovftool). The following manifest will initialize and configure the appliance with embedded database and sso:

vcsa { 'test':
  username => 'root',
  password => 'vmware',
  server   => '192.168.1.10',
  db_type  => 'embedded',
  capacity => 'm',
}

See init.pp for additional options, and 'vpxd_servicecfg help' for additional information.

Known Issues

In vCSA version 5.5 sshd_config MaxSessions needs to be increased above the default value of 1 due to net-ssh opening multiple channels when invoking ssh.exec!