<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Well, I think overall OpenStack has done an absolute shit job of compatibility and I had hoped (and made a huge point of this at the OpenStack conference) Diablo -> Essex would be the end of this compatibility bullshit.<div><br></div><div>But the attitudes in this thread and with respect to the whole Cinder question in general suggest to me that this cavalier attitude towards forward migration hasn't changed.</div><div><br></div><div>So you can kiss my ass.</div><div><br></div><div>-George</div><div><br><div><div>On Jul 12, 2012, at 12:11 PM, Brian Waldon wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">We actually care a hell of a lot about compatibility. We also recognize there are times when we have to sacrifice compatibility so we can move forward at a reasonable pace.<div><br></div><div>If you think we are handling anything the wrong way, we would love to hear your suggestions. If you just want to make comments like this, I would suggest you keep them to yourself.<br><div><br></div><div>Have a great day!</div><div>Brian Waldon<br><div><br><div><div>On Jul 12, 2012, at 9:32 AM, George Reese wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">This community just doesn't give a rat's ass about compatibility, does it?<div><br></div><div>-George</div><div><br><div><div>On Jul 11, 2012, at 10:26 AM, Vishvananda Ishaya wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hello Everyone,<br><br>Now that the PPB has decided to promote Cinder to core for the Folsom<br>release, we need to decide what happens to the existing Nova Volume<br>code. As far as I can see it there are two basic strategies. I'm going<br>to give an overview of each here:<br><br>Option 1 -- Remove Nova Volume<br>==============================<br><br>Process<br>-------<br> * Remove all nova-volume code from the nova project<br> * Leave the existing nova-volume database upgrades and tables in<br> place for Folsom to allow for migration<br> * Provide a simple script in cinder to copy data from the nova<br> database to the cinder database (The schema for the tables in<br> cinder are equivalent to the current nova tables)<br> * Work with package maintainers to provide a package based upgrade<br> from nova-volume packages to cinder packages<br> * Remove the db tables immediately after Folsom<br><br>Disadvantages<br>-------------<br> * Forces deployments to go through the process of migrating to cinder<br> if they want to use volumes in the Folsom release<br><br>Option 2 -- Deprecate Nova Volume<br>=================================<br><br>Process<br>-------<br> * Mark the nova-volume code deprecated but leave it in the project<br> for the folsom release<br> * Provide a migration path at folsom<br> * Backport bugfixes to nova-volume throughout the G-cycle<br> * Provide a second migration path at G<br> * Package maintainers can decide when to migrate to cinder<br><br>Disadvantages<br>-------------<br> * Extra maintenance effort<br> * More confusion about storage in openstack<br> * More complicated upgrade paths need to be supported<br><br>Personally I think Option 1 is a much more manageable strategy because<br>the volume code doesn't get a whole lot of attention. I want to keep<br>things simple and clean with one deployment strategy. My opinion is that<br>if we choose option 2 we will be sacrificing significant feature<br>development in G in order to continue to maintain nova-volume for another<br>release.<br><br>But we really need to know if this is going to cause major pain to existing<br>deployments out there. If it causes a bad experience for deployers we<br>need to take our medicine and go with option 2. Keep in mind that it<br>shouldn't make any difference to end users whether cinder or nova-volume<br>is being used. The current nova-client can use either one.<br><br>Vish<br><br><br>_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></div></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; 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; 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></div></div>_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></div></div></div></div></blockquote></div><br><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></div></body></html>