Does RightScale support Puppet?

Setting up Puppet with RightScale

Steps

1. Create a new Deployment for your Puppet setup.
2. Create a new ServerTemplate and select a desired MCI (for example, RightImage_CentOS_5.4_i386_v5.6 - 11H1.b1). Although we've tested the Puppet setup with the specified CentOS 5.4 RightImage, you may be able to use another OS distribution.  
   Note:  The required Ruby prerequisites will be installed if you use "RightImage_CentOS_5.4_i386_v5.6 - 11H1.b1" which installs Ruby v1.8.5.
3. (Optional) Create an Elastic IP (in the desired AWS region) that you will later associate with the puppetmaster server.  
4. Configure DNS settings.  The next step is to configure a DNS record that points to the puppetmaster server so that the puppetclient server(s) can connect to the puppetmaster.   For alternatives, see http://docs.puppetlabs.com/guides/co...#configure-dns.
   • If you're using DNS Made Easy, you can create a DNS A Record that points to the puppetmaster server.  If you chose to reserve an Elastic IP (EIP), you can point the A Record to the EIP.  If you're not using an EIP, you must update your DNS record later with the IP address that will be assigned to the puppetmaster instance at launch time.  See Domain Setup with DNSMadeEasy.
5. Create an EC2 Security Group with the following port permissions:
   • Open port 8140 for both UDP and TCP using the 0.0.0.0/0 CIDR notation to allow 'any' IPs
6. Create and add the following custom RightScripts as Boot Scripts for the new ServerTemplate.
   • Install Packages - Create a new RightScript that installs the required facter and puppet packages using either your preferred package manager or the RightScript packages line. Alternatively, you can install from source; See http://docs.puppetlabs.com/guides/in...er-from-source and http://docs.puppetlabs.com/guides/in...et-from-source.
   • Configure Puppet - The next step is to make the Manifests and Classes available so that the puppetmaster server will be able to download them.  For example, you could upload your manifests and classes to an S3 bucket and create a RightScript that will download a tarball and copy the files to /etc/puppet/manifests and /etc/puppet/manifests/classes respectively.   For an example manifest, see http://docs.puppetlabs.com/guides/co...-site-manifest.  
     To learn more about creating manifests, see http://projects.puppetlabs.com/proje...nstall_Pattern.
   • Start the Central Daemon - Create a new RightScript that will start the central daemon. 
     See http://docs.puppetlabs.com/guides/co...central-daemon.
7. Create and add the following custom RightScript as an Operational Script of the new ServerTemplate.

   • Connect with puppetmaster - This script will be executed on a Server that will become a puppetclient.  Create a new RightScript that will connect to the puppetmaster by placing the puppetmaster's IP address or FQDN in /etc/sysconfig/puppet. You can either retrieve a preconfigured file for /etc/sysconfig/puppet from an external source, or edit the file directly as part of your script.

8. Add a Server to the Deployment using the new Puppet ServerTemplate.  Call it "puppetmaster" and be sure to select the EC2 Security Group that you created above and the Elastic IP if you're using one.
9. Launch the "puppetmaster" Server and wait for it to become operational. 
10. (Optional) Test your Puppet installation. http://docs.puppetlabs.com/guides/co...g-installation
11. Add another Server to the Deployment using the new Puppet ServerTemplate, except this time name the server "puppetclient" because it will become a client of the puppetmaster.
12. Launch the "puppetclient" Server and wait for it to become operational. 
13. Run the "Connect with puppetmaster" Operational Script on the "puppetclient" server.

You now have a Puppet setup on EC2 that you launched and configured using the RightScale Management Platform.