On 11/19/2014 12:36 PM, Eric Sorenson wrote: > If any one of the main constituent projects having a release would cause a > new AIO to come out, is that the right cycle? Yes, no, maybe, it depends?
Is the proposed plan to roll out a new AIO if PL product versions are unchanged but a vendored product needs to be updated? For example, a Ruby GC fix or an openssl security issue. Things start to get tricky under that scenario if you need to update the AIO to get the vendored product fix but your production env has drifted several PL product versions behind. Doing AIO "bug fix only releases" with the same featured product versions for N-X (where X is at least 2) is a solution but that incurs significant additional release engineering. There is also some dependence on the rate at which hypothetical AIOs would be released. If "things I need to update" was > 2 per month, I'd likely need to get much more formalized about planning roll outs and start skipping over releases. That in and of itself would increase the required amount of pre-production testing because installing a new AIO would mean multiple components are changing at the same time. Better test automation on my part would help (ie, standing up every role type at the same time and for multiple agent runs) but I'd still have hesitation around disturbing the puppet package. My experience has been that there's always glitches with a small % of nodes where agents hang forever, leave uncleaned up lock files, etc. when rolling out new puppet releases that often require mco/pssh intervention. We have a lot of baremetal "special snowflakes" with lots of state so re-provisioning to do orchestration roll outs is a no-go. I've made a histogram of the release timestamps of the product & dependencies RPMs in the EL6 yum repos. The goal was try to get a sense of how many AIO releases there might be in the time frame of a month. https://github.com/jhoblitt/plot-puppet-pkg-releases > > (Do you currently always track the latest package of the Puppet-related > projects you use?) Historically, I've been more or less able to keep up with the ~monthly puppet releases but some other components, especially mcollective, tend to be updated much less frequently. Others, such as theforeman, tend to get "bursty" updates when tracking new/desired features. -Josh -- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/546F74D0.5070205%40cpan.org. For more options, visit https://groups.google.com/d/optout.
