@Daniel Pittman : don't worry about I will call the "assumption" - in a ml, one has always to compromise between describe his all situation (hence, 20 pages mail) or do something rather shorter but clearly spotty. Your answers were quite helpful anyway
@lab42: Your Puppi module sounds quite interesting indeed. I guess I could probably reduce the amount of "junk" in my current puppet configuration using it. I'll look into it in the next days. FYI: As I need to have some kind of "staging auto deploy" for tomorrow, I will just do a crontab job that erase the deployed services every hour. Puppet will notice that (hopefully :) ) and this will trigger a full redeployment. This is far from behind perfect, but this will allow me to have "something working" for the time being. I'll explore Puppi just after that. On 15 January 2011 15:35, Al @ Lab42 <lab42...@gmail.com> wrote: > To manage application deployments I've written this Puppi module: > https://github.com/example42/puppet-modules/tree/master/puppi > it's been designed originally to configure deployments procedures via > puppet but it has > to be run directly from the target node (until I'll write a mcollective > agent) . > So via Puppet you can manage the whole configuration, but not the execution > itself. > > In the project dir there are some examples of deploy procedures that can > adapt to different cases, > (incidentally puppi::project::maven is intended to pull from a Nexus > repository (but it's currenly under redesign and it works just for wars > deploys) > but these can be totally customized or created from scratch using using > custom scripts. > > The advantages I see with this Puppi are: > - A sort of bridge between Puppet and the OS for managing "shot" > operations. > - Standard syntax to manage deploys (and rollbacks) for different cases: > you always have to write: > puppi deploy <name> > - Once configured your deployment templates it's very quick and easy to > setup deploy procedures on different servers with Puppet > - Since the puppi command just executes, in a given seguence, a serie of > commands, these can be totally customized, existing scritps can be adapted > and different scripting languages used. > - The "puppi check" command to see if on your node everything is running > fine is incredibly handy (but for having this to work in an automated way > you need the Example42 monitor classes) > - The notification of the deploy result is customizable. For the moment it > just sends and email, but you can do whatever you may want to do with a > custom script. > > In the future I'd like to integrate Puppi with mcollective and provide a > web frontend, at least for reporting. > But works are in progresss and various things will change. > > Al > > -- > 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<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- Romain PELISSE, *"The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett* http://belaran.eu/wordpress/belaran -- 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.
