Installing and configuring a reference implementation
This guide you walks you through installing and configuring a reference implementation of the Puppet plug-in using Puppet Enterprise 2018.1 or newer and vRA 7.3 or newer. This implementation is designed to create a development environment with vRO, vRA, and Puppet running as quickly as possible in order to help you learn how these tools work together.
The reference implementation isn't designed to be used in a production environment. Once you're familiar with how the plug-in works, you can install it into your production vRO/vRA infrastructure and build compatible workflows and blueprints.
The plug-in works with many implementations of Puppet Enterprise, vRO, and vRA. While you can use these instructions to set up this plugin with other versions of Puppet Enterprise and vRO/vRA, we recommend using this reference implementation the first time through.
Prerequisites
The Puppet plug-in 3.0 is compatible with the following configurations.
You can use the Puppet plug-in 3.0 with vRA 7.3 Enterprise edition, which includes an advanced GUI experience with drag-and-drop Puppetcomponents on blueprints. To do so, you must have:
- A primary server running Puppet Enterprise 2018.1 or newer
- vRealize Automation Enterprise 7.3
- Either internal/external vRO 7.x appliance (vRA includes an internal vRO appliance)
You can also use the plug-in with any vRA version from 6 to 7.3. To do so, you must have:
- A primary server running Puppet Enterprise 2016.4 or newer
- vRealize Orchestrator 6.x or 7.x (vRA includes an internal vRO appliance)
- vRealize Automation 6.x or 7.x
- vRealize Automation Enterprise 7.3 or newer required for GUI integration
Agent nodes being managed by Puppet must run an operating system supported by the Puppet agent.
Network requirements
In order to use vRealize Automation, you must have the correct port configuration for provisioning the primary server, new Linux VMs, and new Windows VMs.
Origin | Destination | Port |
---|---|---|
vRO | Primary server | SSH (22) |
vRO | new Linux VM | SSH (22) |
vRO | new Windows VM | WinRM (5985, 5986) |
new Linux and Windows VMs |
|
|
Removing previous versions of the Puppet plug-in
The plug-in does not currently support upgrades from the previous vRO Puppet plug-in versions.
If you're using any previous version of the plug-in, you must completely remove it before installing a newer version. For best results, delete all puppet elements from the vRO GUI client first and then copy this script from the vRO starter content to the appliance and execute it.
Install and configure Puppet Enterprise
For this reference implementation of the vRO plug-in, you must use a new, clean installation of Puppet Enterprise with Code Manager disabled. After running the setup script, you can opt to enable Code Manager.
Install and configure the Puppet Plug-in
For the reference implementation, we recommend using the vRO built into the vRA appliance.
If you choose to install your own vRO, refer to the vRO documentation. If you previously installed version 1.0 or 2.0 of the plug-in, you must completely remove it before installing version 3.2. The vRO starter content repository includesa script to assist with removing the plug-in.
Related topics: Puppet knowledge base: Removing the Puppet plugin from VMware vRealize Automation
Install the Puppet plug-in
Download and install the Puppet plug-in.
-
Download the Puppet plug-in’s
.vmoapp
package from the VMware Solution Exchange. - Log in to the vRO server’s control center at
https://<VRO-SERVER-IP-ADDRESS>:8283/vco-controlcenter
- Click the Plugins tab.
- Click Install plug-in.
- Install the Puppet plug-in’s
.vmoapp
package downloaded from the VMware Solution Exchange. Read and accept the EULA, then click Install. - After the installation confirmation message appears, click Startup Options in the message reminding you to restart the Orchestrator server. In some versions of vRO this message may not appear, but you still must restart the Orchestrator server.
- On the Startup Options page, click Restart under the Current Status heading.