Why not just come along with me on my next upgrade. You can feel the pain...err excitement, of planning and executing an upgrade in the real world. ;)
On Thu, Aug 24, 2017 at 9:52 AM Ryan Ratliff (rratliff) <rratl...@cisco.com> wrote: > Thanks everyone for the feedback. > > We are looking at ways to make upgrades easier and stories like these are > very helpful. > > -Ryan > > On Aug 24, 2017, at 10:17 AM, Scott Voll <svoll.v...@gmail.com> wrote: > > 1. I'm guessing we are 10% True bugs and 90% environment, but I will agree > with other comments about DNS and NTP being a dumb reason to fail > > 2. as for time, over the years we used to spend over 6 months on > upgrades...... we are down to about 2 months. in our enviroment we have to > document all the changes before so it can be communicated to the end user. > Researching for the answers has moved from Anthony's 100 documents to just > opening a TAC case. It has become way to time consuming to find all the > right doc's to get the correct answer. > > YMMV > > Scott > > > On Wed, Aug 23, 2017 at 1:46 PM, Anthony Holloway < > avholloway+cisco-v...@gmail.com> wrote: > >> Wow, it's kind of cool that you're even asking. Thanks for that. >> >> Already I can see this is going to be a wide gap in responses. Partner vs >> end user, this customer vs that customer, this version vs that version, >> this scenario vs that one, and on, and on, and on. >> >> 1) I feel like it's always a bug (100%), in that, developers should code >> solutions that can work around most issues. E.g., I had an upgrade fail on >> a CUCM because the ntp was 0.us.pool.ntp.org, despite CUCM happily >> syncing to it in the current version. OR Common partition not having >> enough space, when devs could just purge old logs to make room, or simply >> make better logs to begin with (I do admit, moving to compress logs >> [TAR/GZ] was sweet) >> >> 2) This is a painful one for me, but I put in a lot of time preparing for >> an upgrade. A large portion of the time is, in my opinion, wasted finding >> the right documentation and then trying to interpret it. Here's a fun one: >> there's over 100 documents an Engineer needs to reference in preparation >> for what I would consider a low-medium level environment. I've posted this >> before, but I'll post it again, I have a matrix of documents I need to >> reference during the planning and execution phase of an upgrade: >> >> >> >> >> On Wed, Aug 23, 2017 at 8:38 AM Ryan Ratliff (rratliff) < >> rratl...@cisco.com> wrote: >> >>> Quick 2 question poll, feel free to unicast or share your response with >>> the group. >>> >>> 1. When you or your customers have a UCM or IMP upgrade fail, what >>> percentage of failures are due to a bug vs something in the environment >>> (user error, db updates, etc)? >>> % bug: >>> % not a bug: >>> Yes it’s a very subjective question but that’s ok, use your judgement. >>> >>> 2. When an upgrade goes smoothly with no issues, how much time do you >>> put into the planning and preparation for the upgrade (not the execution)? >>> >>> Thanks, >>> >>> -Ryan >>> >>> _______________________________________________ >>> cisco-voip mailing list >>> cisco-voip@puck.nether.net >>> https://puck.nether.net/mailman/listinfo/cisco-voip >>> >> >> _______________________________________________ >> cisco-voip mailing list >> cisco-voip@puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-voip >> >> > >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip