On Dec 22, 2008, at 3:59 PM, Tim Harper wrote: > That's half of the battle. The other half is getting the puppet > master to select the appropriate node configuration. > > I'd like to create the following nodes: > > general > |- www-server > |- db-server > |- sb-server > |- memcache-server > > When I boot up a fresh image, I'd like it to apply the "general" > configuration. Then, I'm going to save the image for future use. > > Later, I'm when I boot up one of the more specialized machines (like > www-server), I'd like it to restore the general configuration, > switch mode to "www-server", and apply the configuration. > > (the need for this approach has been created by us deploying to a > cloud and a static environment during a transitory phase)
You can do a couple of things. One, you can integrate puppet with your EC2 management scripts - that way you know the names of the nodes you launch (via the EC2 API) and can apply configurations normally. This is particularly easy if you have an external node tool - just have your EC2 scripts update the configruation puppet users from external nodes, and move on. If you want to avoid external nodes, I would still tie this in to your EC2 managment - although instead of update an external node tool, just have it update a node.pp file with the correct configuration. Either of these approaches will probably let you use a puppetmasterd that's totally external to EC2 - just have the management scripts verify the SSL cert on demand. Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
