Cloud Assembly supports integration with Puppet Enterprise so that you can manage deployments for configuration and drift.

To integrate Puppet based configuration management, you must have a valid instance of Puppet Enterprise installed on a public or private cloud with a vSphere workload. You must establish a connection between this external system and your Cloud Assembly instance. Then you can make Puppet configuration management available to Cloud Assembly by adding it to appropriate blueprints.

The blueprint service Puppet provider installs, configures, and runs the Puppet agent on a deployed compute resource. The Puppet provider supports both ssh and winm connections with the following prerequisites:

  • ssh connections:

    • Username must be either a super user or a user with sudo permissions to run commands with NOPASSWD.

    • Disable requiretty for the given user.

    • cURL must be available on the deployment compute resource.

  • winm connections:

    • Powershell 2.0 must be available on the deployment compute resource.

    • Configure the Windows template as described in the vRealize Orchestrator documentation.

Shauna is responsible for managing the connections to a Puppet master and for applying Puppets roles, or configuration rules, to specific deployments. Following deployment machines configured to support configuration management are registered with the designated Puppet Master.

When machines are deployed, users can add or delete a Puppet master as an external system or update projects assigned to the Puppet master. Finally, appropriate users can de-register deployed machines from the Puppet master when the machines are decommissioned.