I did an autoscaling pilot some months ago and I needed something similar to this. For the pilot to work (far from the best solution), I was triggering a puppet run on the server (DAS in your case) from the new launched autoscaling instance, using mco as you noted if you have mco working in your instance, or via ssh in my case.
This was just a pilot and I don't need to say the security issues of having mco client enabled on every instance or ssh private keys. On Sunday, April 21, 2013 4:31:57 PM UTC-7, Shiva Narayanaswamy wrote: > > My setup has an EC2 autoscaling group of clustered glassfish application > servers. Each glassfish instance will register itself with a DAS (Domain > Administration Server) to become a member of the cluster, and deregister > itself when it is killed. I was intending to orchestrate this via puppet > exported resources. However I am stuck with trying to figure out how to get > the DAS server to apply puppet configuration everytime an instance is born > in the autoscaling group. > I can schedule puppet to run on the DAS server every 30 minutes, but I > cant afford to wait 30 minutes. I would like to do this as soon as an > instance is provisioned. The only way I can think of doing this is using > mcollective. Am I overlooking something? > > If I havent made myself very clear, please let me know, and I can try to > explain better. > > Looking forward to some design patterns from some experienced gurus! > > Thanks, > Shiva > -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
