Open dmcgrandle opened 4 years ago
I personally think that this driver should be incorporated into Openstack, see #10 This is something I have personally wanted to do - or at very least get it into PyPI, although I haven't had the time to dig back into this as of right now.
Thanks for the response.
This matrix is not dynamically generated. It is maintained by the Cinder team and Vendor driver maintainers. While every effort is made to ensure the accuracy of the data in this matrix, discrepancies with actual functionality are possible. Please refer to your vendor’s support documentation for additional information.
So I think all drivers have an official home outside of OpenStack. However, the Cinder team clearly has some sort of relationship with the driver maintainers to add their driver to their list. I suppose a better way to ask what I was getting at is this - are the driver maintainers of THIS driver planning on starting and maintaining a relationship with the Cinder team in order to get this driver "officially" supported and added to the matrix?
Regards, :D
I think the issue with getting it upstream will be the lack of testing capacity - while I do contribute to the Openstack CI, it will take some work to get proper unit testing for this driver to work. I am not opposed to providing the infra to conduct the tests on, we will need to find a way for maintaining it all long term.
I have a PR open still for many months now just to fix the many pep8 violations....crickets. I doubt this driver works with cinder nowadays.
I'd like to incorporate this driver into OpenStack, but I have a few questions before I invest too much time to do so.
Thanks for your help. :D