Re: [openstack-dev] How to develop a new [Cinder] driver?

2016-07-17 Thread Turbo Fredriksson
On Jul 17, 2016, at 5:40 PM, Jay Bryant wrote: > New drivers need to go into the latest release. Sorry, that's not going to happen. I'm "scared" enough to use Sid/Unstable with Mitaka :D. But to be serious, I'm taking quite a lot of short cuts. That and the fact that my Python isn't really that

Re: [openstack-dev] How to develop a new [Cinder] driver?

2016-07-17 Thread Jay Bryant
Turbo, First, trying to understand why you are trying to create a new driver for Mitaka. New drivers need to go into the latest release. More information can be found here: https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver Second, there really isn't any other way with Python, that

Re: [openstack-dev] How to develop a new [Cinder] driver?

2016-07-15 Thread Turbo Fredriksson
On Jul 15, 2016, at 9:33 PM, Turbo Fredriksson wrote: > Is there a simpler way to do this? A followup question on that: I'm using a remote SAN and I've gotten the creation/deletion/iSCSI share/unshare on that to work just fine. However, when creating a volume from an image, the driver fails on

[openstack-dev] How to develop a new [Cinder] driver?

2016-07-15 Thread Turbo Fredriksson
I'm trying to port the/a Openstack-ZFS driver to Mitaka, but every time I do a change, I have to restart cinder-volume, run my test command, look through the log file, modify the driver, and back to beginning Is there a simpler way to do this? I'm not extremely fluent in Python (it's been over six