On Mon, Dec 22, 2008 at 5:05 PM, Adam Jacob <a...@hjksolutions.com> wrote: > > On Dec 22, 2008, at 3:59 PM, Tim Harper wrote: >> 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) > > Two examples: > > * EC2, Puppet and Capistrano > http://github.com/adamhjk/ec2-cap/tree/master > > * Gentoo, EC2, Portage > http://github.com/dysinger/gec2/tree/master > > Adam
Thank you so much everybody for taking and thought time to respond. I looked in to the git / iClassify / puppet that you mentioned, Adam. That looks very applicable, and at some point we may pursue that route. In light of all suggestions, I think they may be more than I need. What if I developed a custom fact, called it "server_role", stored the value to a yaml filed under /etc/puppet/custom_facts.yml, and then had a default node with a case statement that included the bits of functionality needed for a said role? Has anybody done that before? Am I crossing into illegal territory? Thanks, Tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
