Thanks to everyone who's replied so far (and please, keep the ideas coming!); it's really useful looking at all the various approaches that people are taking.
I think so far I like Tim's variation on Andreas' approach the best, though I think that if/when we have more AMIs running, Dave's puppetmaster-in-the-cloud has some compelling advantages. I look forward to trying a few of these options out in the next few weeks to see what works best for us. Thanks again Chris On Sep 15, 9:35 am, Matt <mattmora...@gmail.com> wrote: > 2009/9/14 dmangot <dman...@terracottatech.com>: > > > > > > > On Sep 11, 5:07 am, Chris <chrisma...@gmail.com> wrote: > >> Hi all, > > >> I'm starting to use EC2, and I'm after some examples of best practices/ > >> tips and tricks from folk with more experience of the Puppet/EC2 combo > >> than me: > > >> We're starting by using EC2 for testing and development purposes. This > >> means that we won't be running our instances full-time; rather, we'll > >> be spinning them up and down for a few hours at a time, as and when > >> needed. I'd like the instances to call back to my local puppetmaster > >> to configure themselves post-boot. > > > Chris, > > > I did exactly this. Check out my blog post: > > >http://tech.mangot.com/roller/dave/entry/on_running_terracotta_on_ec2 > > > Works great. > > > Cheers, > > > -Dave > > I went along with a slightly different route. > > 1) Puppetmaster in datacentre exposed with an external DNS. > 2) Ruby scipts to start the EC2 instances and create a puppet nodes > manifest file with the internal DNS names. > 3) Another script then parses for the internal DNSs and cleans the > certs on the master, along with removing any existing manifest for > that node. > 4) cron job script that polls EC2 account for instances and removes > ones in the nodes/ec2 directory that are no longer running. > > I've recently rebuilt the AMI and changed the EC2 starting scripts to > contain both a URL for the puppet client rpms and the puppet.conf data > in the EC2 userdata. This way we don't need multiple AMIs for > different puppetmasters or different versions of the puppet client. > > Would have loved to talk more about this stuff at puppet camp, shame > i'm unlikely to be able to make it. > > Cheers, > > Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
