Forge Home

vshield

VMware vShield puppet module

10,816 downloads

9,039 latest version

3.5 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.5.0 (latest)
  • 0.0.1
released Apr 21st 2015

Start using this module

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

Add this module to your Puppetfile:

mod 'vmware-vshield', '0.5.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

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

Manually install this module globally with Puppet module tool:

puppet module install vmware-vshield --version 0.5.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
Tags: vmware, vshield

Documentation

vmware/vshield — version 0.5.0 Apr 21st 2015

VMware vShield module

This module manages resources in VMware vCloud Network and Security 5.1 (vCNS), i.e. vShield.

Description

VMware vCloud Network and Security is deployed via a virtual appliance. The module is able to attach vCNS to a vCenter and manages vCNS 5.1 resources via vShield API through REST.

+------------+         +--------+
|            | vSphere |  vCSA  | <-
|   Puppet   | +-----> +--------+  |
| Management |                     | register
|    Host    | vShield +--------+  |
|            | +-----> |  vCNS  | --
+------------+         +--------+

Installation

$ puppet module install vmware/vshield

Usage

Two transport connection is required for managing vShield resources, since vShield is dependent on a vCenter:

transport { 'vshield':
  username => 'admin',
  password => 'default',
  server   => 'vshield.lab'
}

transport { 'vcenter':
  username => 'root',
  password => 'vmware',
  server   => 'vcenter.lab',
  options  => { 'insecure' => true, },
}

Establishing connection to vCenter is specified by vshield_global_config:

vshield_global_config { 'vshield.lab'
  vc_info   => {
    ip_address => 'vcenter.lab',
    user_name  => 'root',
    password   => 'vmware',
  },
  time_info => { 'ntp_server' => 'us.pool.ntp.org', }
  dns_info  => { 'primary_dns' => '8.8.8.8' },
  transport => Transport['vshield'],
}

The vCenter transport server attribute must match vshield_global_config[vc_info][ip_address] returned by the vShield API. Connectivity to vCenter is necessary to translate resource (such as a datacenter, esx host, or folder name) to vSphere Managed Object Reference (MoRef) required by the vShield API.

vshield_edge can be deployed to compute resource in a datacenter:

vshield_edge { 'vshield.lab:edge_dmz':
  ensure           => present,
  datacenter_name  => 'datacenter_1',
  compute          => 'cluster_dmz_1',
  enable_aesni     => false,
  enable_fips      => false,
  enable_tcp_loose => false,
  vse_log_level    => 'info',
  fqdn             => "edge.dmz.lab",
  transport        => Transport['vshield'],
}

See tests folder for additional examples.