<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div>I would tend to agree that the overall installation process could improve (not that I want to give up my ANSI art or anything). Most of the installation process today is merely an extension of the underlying Linux kernel. I would settle for more verbose
feedback when errors are encountered, like dumping the syslog to the tmp folder on a jailed CLI that I have access to at all points during the install instead of the rain dance you have to do today with the serial port.<br>
<br>
-RH</div>
<div><br>
On Aug 23, 2017, at 4:47 PM, Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">Wow, it's kind of cool that you're even asking. Thanks for that.
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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
<a href="http://0.us.pool.ntp.org">0.us.pool.ntp.org</a>, 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)</div>
<div><br>
</div>
<div>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:</div>
<div><br>
</div>
<div><img src="http://cisco-voip.markmail.org/download.xqy?id=rrs3zlxbamemgodr&number=1"> <br>
<br>
<div class="gmail_quote">
<div dir="ltr">On Wed, Aug 23, 2017 at 8:38 AM Ryan Ratliff (rratliff) <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Quick 2 question poll, feel free to unicast or share your response with the group.<br>
<br>
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)?<br>
% bug:<br>
% not a bug:<br>
Yes it’s a very subjective question but that’s ok, use your judgement.<br>
<br>
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)?<br>
<br>
Thanks,<br>
<br>
-Ryan<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
</div>
</blockquote>
</body>
</html>