On 8/26/2014 12:41 PM, Alex Demitri wrote:
Hi guys - i am fairly new to puppet and i am trying to figure out ways to implement it in my organization to make good use of it. One thing we thought would be useful to better our deployment process, is to add a mechanism that would have a vanilla server getting installed on a VM, boot up, check into puppet and figure out these three questions:1) Where am I? - in what Datacenter/Availability zone am I? Based on that, what syslog servers do i have to use, NTP servers, etc.. 2) Who am I? - what server am i? What files do i need for basic functions? 3) What am I supposed to do? - based on what server I am, what am i supposed to do? do i have to run Tomcat? Apache? And if yes, where are my configuration files? In short, find a holistic way for a system to come up to speed by itself. I already thought of using meaningful hostnames for the roles of the servers but that does not work well in the cloud... Thoughts? Thanks! Alex
When we provision machines the system passes a few flags that do the equivalent of
sudo FACTER_role=frontend puppet agent --environment stage --certname fe34.usw1.example.com
role is a custom fact that needs to be set the first time as shown above. Puppet does the Hiera lookup based on $role and $env with $certname or nodename as the final arbiter. That's as much config as we need, but no reason you couldn't add various ec2 facts to the hierarchy.
Ramin -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53FD6F90.6060601%40badapple.net. For more options, visit https://groups.google.com/d/optout.
