Re: [Puppet Users] Puppet vs "typical" release management / change management

2014-02-04 Thread Gareth Rushgrove
On 4 February 2014 14:11, Jason Antman wrote: > Steve, > > I'll leave it up to others to answer your question more directly, as I'm not > sure I really can - it's been a while since I worked in an ITIL shop. What I > will say, though, since inevitably *someone* will, is that ITIL contains > some g

Re: [Puppet Users] Puppet vs "typical" release management / change management

2014-02-04 Thread Jason Antman
Steve, I'll leave it up to others to answer your question more directly, as I'm not sure I really can - it's been a while since I worked in an ITIL shop. What I will say, though, since inevitably *someone* will, is that ITIL contains some good concepts and some bad ones. Overall, I'd never wo

Re: [Puppet Users] Puppet vs "typical" release management / change management

2014-02-04 Thread José Luis Ledesma
We are currently setting up puppet in our infrastructure. We have a very enforcing change management process. Moreover, is impossible to make changes in all the development servers at the same time, so using the standard Dev, test, pre, pro environments is not an options. We have decided to work

[Puppet Users] Puppet vs "typical" release management / change management

2014-02-04 Thread Steven James
Hi there. I'm look to see if anybody has any advice to share around how the implementation of Puppet affects the "typical" ITIL based release management and change management processes. >From a change perspective, I'm thinking that the whole risk thing associate with the CAB for example, should