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 get a whole lot better as a result of version controlled infrastructure manifests, ability to provide infrastructure code diffs, noop runs against bare metal, with the option of running a few noop runs against current patch set...will probably help. How else does the ITIL base change process have to typically (er) change...to accommodate the devops approach? Similar question for release management. How does the introduction of Puppet typically affect the release management process? Any input greatly appreciated. SteveJames -- 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/CAB_ORUv5NbgL-L4SattZ5y5V9G0r4BHgfVx6Pd-WVp8frHcdXg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
