Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cinder Driver support #19

Open
dmcgrandle opened this issue May 31, 2020 · 4 comments
Open

Cinder Driver support #19

dmcgrandle opened this issue May 31, 2020 · 4 comments
Assignees
Labels

Comments

@dmcgrandle
Copy link
Contributor

I'd like to incorporate this driver into OpenStack, but I have a few questions before I invest too much time to do so.

  1. Why is this driver not in the list of supported drivers maintained by OpenStack: https://docs.openstack.org/cinder/ussuri/reference/support-matrix.html#driver-support-matrix
  2. That same document lists 11 required functions any Cinder driver must support. Does this driver support all of them, especially the last one (Volume Migration)?
  3. If I run into issues is it best to post them here as issues, or will I get more support on the FreeNAS community forums?

Thanks for your help.
:D

@hbonath
Copy link
Contributor

hbonath commented Jun 1, 2020

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.

  1. This driver is not maintained by Openstack. This is its official home.
  2. I can attest to support for the top 10 functions in that list, although I have never tested migration, is this the functionality you are referring to?
  3. As I mentioned in 1, this repo is the driver's official home.

@dmcgrandle
Copy link
Contributor Author

Thanks for the response.

  1. I think each vendor maintains their own official home. In the link I referenced above they basically state that when they said this in a note:

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?

  1. Thanks for verifying this. Yes, the link you gave leads to a description of exactly the functionality I was referring to. 👍

Regards,
:D

@donnydavis
Copy link
Contributor

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.

@hemna
Copy link
Contributor

hemna commented Dec 28, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants