Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > ServerTemplates > Infinity > ST > Puppet Client Beta (v13 Infinity) > Puppet Client Beta (v13 Infinity) - Tutorial

Puppet Client Beta (v13 Infinity) - Tutorial

 icon-Beta-v1.png  Service-level response times are the same as for general-release features. Although this new feature/technology has undergone significant testing and is not expected to change significantly prior to general release, the use of this feature/technology is not recommended for production environments. You are encouraged to use this feature/technology for development and testing purposes only.  

Table of Contents    


Leading edge features

    ►  Tutorial



To set up a Puppet Client in a public or private cloud environment. The Puppet Client connects either to the Puppet Master inside or outside RightScale. 


The following are prerequisites for completing this tutorial:

  • 'actor', 'designer', and 'library' user role privileges in the RightScale account
  • For Amazon EC2, Google, and other clouds that support security groups, you must have a security group defined with TCP port 22 open for SSH access and any other port and protocol access required by your application. Also, remember that iptables is installed by default on all servers, as described in the Security section of this tutorial.
  • Puppet Master is up and running and is reachable.


This tutorial describes the steps for launching one or more Puppet Clients in the cloud.


Create Puppet Client

Follow these steps to add Puppet Client to the deployment.

  1. Go to the MultiCloud Marketplace (Design > MultiCloud Marketplace > ServerTemplates) and import the most recently published revision of the following ServerTemplate into the RightScale account.
    • Puppet Client Beta (v13.x)   (Note: This ServerTemplate was deprecated from the MultiCloud Marketplace and can no longer be imported.)
  2. Typically, most users will want to customize their Puppet Client ServerTemplate. Click the Clone button to create an editable version of the ServerTemplate. Rename the ServerTemplate accordingly. (e.g. My Puppet Client)
  3. Before you make any changes to the ServerTemplate, click the Commit button so that the first revision of the ServerTemplate matches the original revision, which will make it easier to perform differentials in the future to see what changes were made to the "original" version. When committing the ServerTemplate you can use a simple commit message. (e.g. Original version. No changes.)
  4. While viewing the HEAD version of the editable ServerTemplate, click the Add Server button.
    • Note: For production environments, you should always use committed revisions of ServerTemplates to launch servers. However, if you are actively developing and testing the ServerTemplate, it's helpful to launch servers with a HEAD version of the ServerTemplate so that you can easily add alerts and/or scripts to the template for performing tests on a running Puppet Client server.
  5. Select the cloud for which you will configure a server.
  6. Select the deployment into which the new server will be placed, then click Continue
  7. Next, the Add Server Assistant wizard will walk you through the remaining steps that are required to create a server-based on the selected cloud.
    1. Server Name - Provide a nickname for your new Puppet Client (eg. Puppet Client 1).
    2. Select the appropriate cloud-specific resources that are required in order to launch a server into the chosen cloud. The required cloud resources may differ depending on the type of cloud infrastructure. If the cloud supports multiple datacenters / zones, select a specific zone.
  8. Click Confirm, review the server's configuration and click Finish to create the server.

Configure Inputs

The next step is to define the properties of your Puppet Client by entering values for inputs. It is best to do this at the deployment level. For a detailed explanation of how inputs are defined and used in Puppet recipes and RightScripts, see Inputs and their Hierarchy.
To enter inputs for the Puppet recipes that will run on your Puppet Client, open the your deployment > Inputs tab and click Edit, then follow the directions below to configure input values. We recommend that you set up credentials for password values and any other sensitive data as shown in the examples.
Note: The following examples and sample values assume that you will connect the Puppet Master inside or outside RightScale. Please refer to the runbook for proper setup instructions.

Input Name Description Example Value
Puppet Client Version Specify the Puppet Client version to match the requirements of your Puppet Master text: 2.7.13-1
Client Node Name Name which will be used to authenticate the Puppet Client on the remote Puppet Master. Instance FQDN will be used if nothing is specified. text:
Puppet Master FQDN Enter the address of the remote Puppet Master server that the server is connecting to. text:
Puppet Master Port Enter the port in use by the remote Puppet Master server. text: 8140
Puppet Client Environment Specify the environment type for the Puppet Client configuration. text: development

Launch the Server

After configuring the inputs, launch the Puppet Client. Refer to the instructions in Launch a Server if you are not already familiar with this process.

You must to post a comment.
Last modified
09:25, 28 Apr 2014



This page has no classifications.



© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.