You either need to comment out the enabled_backends line, or you'll want
to put something similar to this in your cinder.conf file:
[DEFAULT]
...
enabled_backends = cloudbyte
...
[cloudbyte]
volume_driver = volume_driver =
cinder.volume.drivers.cloudbyte.cloudbyte.ElasticenterISCSIDriver
Can the default_volume_type be left empty and get the original None
type, so we don't have to create the volume type prior to running tempest
tests?
Andrew Kerr
OpenStack QA
Cloud Solutions Group
NetApp
On 8/14/14, 5:23 PM, Martin, Kurt Frederick (ESSN Storage MSDU)
kurt.f.mar...@hp.com wrote:
Hi cinder,
Just noticed we have competing solutions to implement extend_volume in the
generic NFS driver [1] [2]. I understand these are not targeted until
after RC1, but I also didn't want the duplicate effort lost in the
shuffle. Are there any thoughts on which is the more appropriate
On 7/2/14, 11:00 AM, Anita Kuno ante...@anteaya.info wrote:
On 07/01/2014 01:13 PM, Asselin, Ramy wrote:
3rd party ci names is currently becoming a bit controversial for what
we're trying to do in cinder: https://review.openstack.org/#/c/101013/
The motivation for the above change is to aid
Hi Deepak,
I know that there are plans to completely change how NFS uses (or more
accurately, will not use) the shares.conf file in the future. My guess is
that a lot of this code will be changed in the near future during that
rework.
Andrew Kerr
OpenStack QA
Cloud Solutions Group
NetApp
The NetApp driver uses NetApp specific API calls to implement the actual
cloning of the file. You could probably generalize it by implementing the
keeping of a cached image file on the destination share for future copies,
and then implement a standard copy file method that could be overloaded
by
The problem is in the version of taskflow that is downloaded from pypi by
devstack. You will need to wait until a new version 0.10.0 is available [1]
[1] https://pypi.python.org/pypi/taskflow/
Andrew Kerr
OpenStack QA
Cloud Solutions Group
NetApp
From: Bharat Kumar
Hi all,
The physical equipment that runs the NetApp CI system is scheduled to be moved
to a new building next week. In order to accommodate this move we will be
taking the NetApp CI system offline at EOB on Friday Jan 15 and plan to have it
back up and running by EOB on Monday Jan 25.
I just
