<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 12, 2012, at 5:08 PM, John Postlethwait wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div style="font-family: Helvetica; font-size: 12px; ">So, in short, your entire purpose here is to troll everyone? Nice… : /</div><div style="font-family: Helvetica; font-size: 12px; "><br></div></blockquote><div><br></div>If you think that, you're likely part of the problem.</div><div><br><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; ">You obviously care. You keep responding… You have been asked numerous times what we can do to NOT "<span style="font-size: 13px; ">stick us yet against in this situation in the future." </span> Why is that such a difficult question to answer? Do you have an answer? Is your answer to "not change anything, ever"? That is not likely or reasonable – so what can be done here? Have you seen the other thread about what this cinder/nova-volume change entails?</div><div style="font-family: Helvetica; font-size: 12px; "><br></div></blockquote><div><br></div><div>This is an idiotic question. What can I suggest everyone do about as yet unproposed changes to OpenStack? Seriously?</div><br><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; ">There ARE people here willing to hear it out if you have an answer, or an actionable suggestion, or process, or SOMETHING besides "get your heads out of your asses," which is hardly actionable, as it is vague and hopefully not a literal belief/suggestion…</div><div style="font-family: Helvetica; font-size: 12px; "><br></div><div style="font-family: Helvetica; font-size: 12px; ">So, George: What do you want from us here? You likely have some legitimate pain-points, concerns, and reasons to be upset, but they are absolutely lost in your angry and personally offensive responses. Can you maybe elaborate on what pain THIS change would cause, and how we might assuage that?</div><div style="font-family: Helvetica; font-size: 12px; "><br></div></blockquote><div><br></div>This community needs offending.</div><div><br></div><div>How many years has it been? How many OpenStack upgrades can you point to that have been painless? How many interoperable, multi-vendor OpenStack clouds? How reliable is the API as an appropriate abstract representation of an OpenStack implementation that can be used to build an ecosystem?</div><div><br></div><div>The answer to those questions is:</div><div><br></div><div>- 3</div><div>- 0</div><div>- 0</div><div>- not at all</div><div><br></div><div>It is very clear that compatibility and upgradability is a huge issue. And a number of people, obviously including you, don't seem to grasp that.</div><div><br></div><div>We have silly comments like Michael's "I hate to fan the fire, but what would happened in cassandra if they _never_ updated their data structures."</div><div><br></div><div>1. Obviously I am not talking about never changing anything. Any suggestion otherwise is being willfully obtuse.</div><div>2. There's a big difference between systems like Cassandra that generally can have maintenance windows and environments like clouds which should NEVER have maintenance windows</div><div>3. Every single other cloud platform on the planet manages to support a much less painful upgrade path with a much higher level of interoperability.</div><div><br></div><div>In all of yours and Jon's and Brian's nonsense, I don't see any actual defense of the compatibility and interoperability of OpenStack deployments. I can only assume that's because you can't actually defend it, yet you nevertheless have your head stuck in the sand.</div><div><br></div><div>-George</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>--<br>George Reese - Chief Technology Officer, enStratus<br>e: <a href="mailto:george.reese@enstratus.com">george.reese@enstratus.com</a> Skype: nspollution t: @GeorgeReese p: +1.207.956.0217<br>enStratus: Enterprise Cloud Management - @enStratus - <a href="http://www.enstratus.com/">http://www.enstratus.com</a><br>To schedule a meeting with me: <a href="http://tungle.me/GeorgeReese">http://tungle.me/GeorgeReese</a></div></div></span></span>
</div>
<br></body></html>