[Puppet Users] Re: Automating removal of an application

2009-01-30 Thread Eric Gerlach
On Fri, Jan 30, 2009 at 02:12:03PM +1100, Daniel Pittman wrote: > > nicolas writes: > > > For these applications, we need to have a very good control. So we'll > > never update them via local update utility nor use an ensure => latest > > We always use ensure => x.y.z > > We also need to be abl

[Puppet Users] Re: Automating removal of an application

2009-01-30 Thread nicolas
Ok, I think I understand better how we should do now. However, the use of version in class name is still mandatory for us because we may have two versions of an application in production at same time (on different nodes) and need to have very strict control on installed versions. Also, we generat

[Puppet Users] Re: Automating removal of an application

2009-01-29 Thread Daniel Pittman
nicolas writes: > For these applications, we need to have a very good control. So we'll > never update them via local update utility nor use an ensure => latest > We always use ensure => x.y.z > We also need to be able to do rollback, so it's simpler to remove > everything from say, version 1-3-

[Puppet Users] Re: Automating removal of an application

2009-01-28 Thread Andrew Shafer
I'm not entirely certain of your scenario, but unless you are going to purposely have two versions of the same application running in production for extended periods, this seems like the wrong way to do this. Do you have some way to roll through Dev, Test, Staging, Production? Can you just have o

[Puppet Users] Re: Automating removal of an application

2009-01-28 Thread nicolas
Ok, I agree that my request is targeted to a special case that can be dangerous if applied to general case. My main concern was that our admins may find tedious to do the two- steps process for each release of an application. Maybe I should tell them it's more secure ! Anyway, thanks for sharing

[Puppet Users] Re: Automating removal of an application

2009-01-28 Thread Evan Hisey
On Wed, Jan 28, 2009 at 3:00 AM, nicolas wrote: > > > Thanks for your answer Evan. > > For these applications, we need to have a very good control. So we'll > never update them via local update utility nor use an ensure => latest > We always use ensure => x.y.z > We also need to be able to do rol

[Puppet Users] Re: Automating removal of an application

2009-01-28 Thread nicolas
Thanks for your answer Evan. For these applications, we need to have a very good control. So we'll never update them via local update utility nor use an ensure => latest We always use ensure => x.y.z We also need to be able to do rollback, so it's simpler to remove everything from say, version 1

[Puppet Users] Re: Automating removal of an application

2009-01-27 Thread Mike Renfro
Evan Hisey wrote: > About the only time you need to do a wholesale application removal is > when you want to remove it from a system. If you have lots of > applications that are just ugly to install an dremove you may want to > take a look at Stow. If you use stow, you may want my stowedpackage

[Puppet Users] Re: Automating removal of an application

2009-01-27 Thread Evan Hisey
On Mon, Jan 26, 2009 at 10:18 AM, nicolas wrote: > > Hello, > > I'm currently prototyping the use of Puppet to manage a bunch of > home-made applications on a lot of servers. > As our applications evolves frequently and multiples versions can > be used at the same time, we use classes that in