<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I would like to add that the complete lack of documentation makes the VSA code unusable. I have no idea where to get started with it. The following bug has been open and assigned for the past 6+ months: <a href="https://bugs.launchpad.net/nova/+bug/835099">https://bugs.launchpad.net/nova/+bug/835099</a>. The fact that you are maintaining a fork of Nova with your own enhancements also reinforces the idea that VSA should not live within the Nova codebase. We are also in our release-candidate phase, so any major code 'enhancements' should *not* be landing.<div><div><br></div><div>Brian<br><div><br></div><div><br><div><div>On Mar 15, 2012, at 8:56 AM, Vishvananda Ishaya wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Vladimir,<br><br>Are you sure the code in trunk is working? Investigation by one of the community members showed that it was broken. If you are planning on merging your new code in, perhaps it is better to do it all at once? FYI, nova-volume is going to be split into its own service during folsom, and based on the fact that vsa uses both compute and volume, it might be best to actually move it into its own project as well.<br><br>This will keep separation of concerns and allow you to maintain it more directly in the public. I still think the best approach for now is to pull it and bring back the fully functional version in Folsom. No one is using it in its current state.<br><br>Vish<br><br>On Mar 15, 2012, at 8:48 AM, Vladimir Popovski wrote:<br><br><blockquote type="cite">Hi Vish & All,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We would definitely prefer to leave the code in place and ready to fix any<br></blockquote><blockquote type="cite">issues related to it.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We found out that it is extremely hard to work with latest trunk version -<br></blockquote><blockquote type="cite">our QA was constantly complaining about different regression scenarios and<br></blockquote><blockquote type="cite">we decided to stick with released stable Nova branches and perform merges<br></blockquote><blockquote type="cite">either after main releases or major milestones.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The current VSA code in trunk is completely functional & working. We've<br></blockquote><blockquote type="cite">done tons of enhancements to it and added new functionality during last<br></blockquote><blockquote type="cite">4-5 month. As I mentioned before our plan was to merge it with latest<br></blockquote><blockquote type="cite">relatively stable Essex code and to have this code in somewhere at the<br></blockquote><blockquote type="cite">beginning of Folsom.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">At the same time we understand your concerns - without proper<br></blockquote><blockquote type="cite">documentation and related packages (like VSA image & drive discovery<br></blockquote><blockquote type="cite">packages) it is very hard to use/test it.<br></blockquote><blockquote type="cite">We are ready to collaborate with whoever is interested in order to make<br></blockquote><blockquote type="cite">this functionality generic enough. From our side we will try to fix it.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Please let us know what should we do in order to leave it in place.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks,<br></blockquote><blockquote type="cite">-Vladimir<br></blockquote><blockquote type="cite">Zadara Storage<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-----Original Message-----<br></blockquote><blockquote type="cite">From: <a href="mailto:openstack-bounces+vladimir=zadarastorage.com@lists.launchpad.net">openstack-bounces+vladimir=zadarastorage.com@lists.launchpad.net</a><br></blockquote><blockquote type="cite">[mailto:openstack-bounces+vladimir=<a href="mailto:zadarastorage.com@lists.launchpad.net">zadarastorage.com@lists.launchpad.net</a>]<br></blockquote><blockquote type="cite">On Behalf Of Vishvananda Ishaya<br></blockquote><blockquote type="cite">Sent: Wednesday, March 14, 2012 6:54 PM<br></blockquote><blockquote type="cite">To: <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a> (<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>)<br></blockquote><blockquote type="cite">Subject: [Openstack] Removal of VSA Code<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Apologies if you receive this email twice, I sent the first one from the<br></blockquote><blockquote type="cite">wrong address.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hello Everyone,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Last week during the release meeting it was mentioned that the VSA code is<br></blockquote><blockquote type="cite">not working properly and we should either fix it or remove it. I propose<br></blockquote><blockquote type="cite">to remove it for the following reasons:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">* Lack of documentation -- unclear how to create a vsa image or how the<br></blockquote><blockquote type="cite">image should function<br></blockquote><blockquote type="cite">* Lack of support from vendors -- originally, the hope was other vendors<br></blockquote><blockquote type="cite">would use the vsa code to create their own virtual storage arrays<br></blockquote><blockquote type="cite">* Lack of functional testing -- this is the main reason the code has<br></blockquote><blockquote type="cite">bitrotted<br></blockquote><blockquote type="cite">* Lack of updates from original coders -- Zadara has mentioned a few times<br></blockquote><blockquote type="cite">that they were going to update the code but it has not happened<br></blockquote><blockquote type="cite">* Eases Transition to separate volume project -- This lowers the surface<br></blockquote><blockquote type="cite">area of the volume code and makes it easier to cleanly separate the volume<br></blockquote><blockquote type="cite">service to compute<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">As far as I can tell Zadara is maintaining a fork of the code for their<br></blockquote><blockquote type="cite">platform, so keeping the code in the public tree doesn't seem necessary.<br></blockquote><blockquote type="cite">I would be happy to see this code come back in Folsom if we get a stronger<br></blockquote><blockquote type="cite">commitment to keep it up-to-date, documented, and maintained, and there is<br></blockquote><blockquote type="cite">a reasonable location for it if the volume and compute code is separate.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">If anyone disagrees, please respond ASAP.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Vish<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br></blockquote><blockquote type="cite">Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br></blockquote><blockquote type="cite">Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br></blockquote><blockquote type="cite">More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote><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></div></div></body></html>