The Puppet plug-in Samples workflows show how you can combine the workflows and create custom processes.

You can find these workflows on the Workflows view of the Orchestrator client, in the Samples subdirectory of the Puppet plug-in library.

These workflows automate the following tasks:

  • Installing and configuring the Puppet agent.

  • Registering the Puppet agent certificates with the Puppet Master.

  • Classifying the node with a class or multiple classes on the Puppet Master.

  • Triggering an on-demand Puppet run of the Puppet agent on the newly configured node.

Note:

While vRealize Orchestrator is querying the Puppet Master class parameter list to populate a newly set parameter, the vRealize Orchestrator user interface becomes unresponsive for 10 seconds.

Table 1. Samples Workflows

Workflow

Description

Single Class - Install, Configure, Sign, Classify and Remediate Node

Shows how you can connect multiple Puppet workflows to automate the process of adding and classifying a Puppet node.

To run this workflow, complete the following parameters:

  • Add a Puppet Master that was registered in the vRealize Orchestrator inventory in the Puppet Master text box.

  • Define an environment that the Puppet node belongs to such as test, QE, or production.

  • Select a Manifest, Hiera, or experimental Rake classification from the drop-down menu.

    Set the applicable parameters for the classification type. See Using the Puppet Plug-In Manifest Workflows, Using the Puppet Plug-In Hiera Workflows, or Experimental Puppet Plug-In Features.

    Note:

    After you set a classification type for a node, do not use another classification type on that node.

  • Select an agent action from the Puppet Agent Setup Action drop-down menu.

    The None action applies to a node that has an agent installed and configured with the Puppet Master. The node name for this action refers to the Puppet node to classify.

    The Install, Configure, and Sign action lets you automate installing the agent, configuring with the Puppet Master, and signing a node certificate request on the Puppet Master for a new node.

    The Configure and Sign action lets you automate the configuring with the Puppet Master, and signing a node certificate request on the Puppet Master for a node with the agent preinstalled.

    The Sign action lets you automate the signing of a node certificate request on the Puppet Master for an existing node. The node name for this action refers to the Puppet node to classify.

  • Accept the default setting to trigger an on-demand Puppet agent run.

  • Select the node operating system from the Machine Type drop-down menu.

    Set the applicable parameters for the operating system. See Using the Puppet Plug-In Node Management Workflows.

  • (Optional) Override the default Puppet agent download path in the Installer Base URL override text box.

    For example, the default agent download URLs for Puppet Open Source are http://yum.puppetlabs.com and http://apt.puppetlabs.com.

    For Puppet Enterprise, the Administrator must install the appropriate agent package from the Puppet Master package repository on the Puppet Master.

    The default Windows agent download URL for the Puppet Enterprise is https://s3.amazonaws.com/pe-builds/released and the Puppet Open Source is https://downloads.puppetlabs.com/windows.

  • (Optional) Click Yes to register the Puppet Master host name to the IP address in the node hosts file.

  • (Optional) Click Yes to replace the existing classification information.

  • (Optional) Enter the class to add to the Puppet node.

    For example, you can use the Apache or Tomcat class.

  • (Optional) Override the default class parameters.

    To override the parameter value remove the prefix default and the parentheses and add a new value. For example, the class parameter default (80) value changes to 90.

Multiple Classes - Install, Configure, Sign, Classify and Remediate Node

Shows how you can connect multiple Puppet workflows to automate the process of adding a node to your Puppet environment and classify multiple classes at the same time.

To run this workflow, complete the following parameters:

  • Add a Puppet Master that was registered in the vRealize Orchestrator inventory in the Puppet Master text box.

  • Define an environment that the Puppet node belongs to such as test, QE, or production.

  • Select a Manifest, Hiera, or experimental Rake classification from the drop-down menu.

    Set the applicable parameters for the classification type. See Using the Puppet Plug-In Manifest Workflows, Using the Puppet Plug-In Hiera Workflows, or Experimental Puppet Plug-In Features.

    Note:

    After you set a classification type for a node, do not use another classification type on that node.

  • Select an agent action from the Puppet Agent Setup Action drop-down menu.

    The None action applies to a node that has an agent installed and configured with the Puppet Master. The node name for this action refers to the Puppet node to classify.

    The Install, Configure, and Sign action lets you automate installing the agent, configuring with the Puppet Master, and signing a node certificate request on the Puppet Master for a new node.

    The Configure and Sign action lets you automate the configuring with the Puppet Master, and signing a node certificate request on the Puppet Master for a node with the agent preinstalled.

    The Sign action lets you automate the signing of a node certificate request on the Puppet Master for an existing node. The node name for this action refers to the Puppet node to classify.

  • Accept the default setting to trigger an on-demand Puppet agent run.

  • Select the node operating system from the Machine Type drop-down menu.

    Set the applicable parameters for the operating system. See Using the Puppet Plug-In Node Management Workflows.

  • (Optional) Override the default Puppet agent download path in the Installer Base URL override text box.

    For example, the default agent download URLs for Puppet Open Source are http://yum.puppetlabs.com and http://apt.puppetlabs.com.

    For Puppet Enterprise, the Administrator must install the appropriate agent package from the Puppet Master package repository on the Puppet Master.

    The default Windows agent download URL for the Puppet Enterprise is https://s3.amazonaws.com/pe-builds/released and the Puppet Open Source is https://downloads.puppetlabs.com/windows.

  • (Optional) Click Yes to register the Puppet Master host name to the IP address in the node hosts file.

  • (Optional) Click Yes to replace the existing classification information.

  • (Optional) Enter the classes to add to the Puppet node.

    For example, you can use the Apache and Tomcat classes.

  • (Optional) Override the default class parameters.

    To override the parameter value remove the prefix default and the parentheses and add a new value. For example, the class parameter default (80) value changes to 90.