On 26 June 2014 05:46, Amit Das amit@cloudbyte.com wrote:
This seems cool.
Does it mean the storage vendors write their new drivers just map it from
cinder.conf ?
Correct. You can cause devstack to set up cinder.conf for you by
setting CINDER_DRIVER=cinder.volume.drivers.foo.bar in
Hi All,
I am observing a bit difference in manager.py file between these branches
stable/icehouse and master.
In stable/icehouse various driver mapped in manager.py but it is not in
master.
Please guide me, where i have to map my driver.
*Thanks Regards*,
Yogesh Prasad.
That's easy; you don't. The mappings are their because we moved some
drivers round during a code cleanup and didn't want old config files
to break during an upgrade. The old names have been deprecated since
Falsom and finally now removed; new drivers don't need to do any
mapping at all.
On 25
This seems cool.
Does it mean the storage vendors write their new drivers just map it from
cinder.conf ?
Does it involve any changes to devstack as well ?
Regards,
Amit
*CloudByte Inc.* http://www.cloudbyte.com/
On Wed, Jun 25, 2014 at 7:22 PM, Duncan Thomas duncan.tho...@gmail.com
wrote: