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:

enabled_backends = cloudbyte
volume_driver = volume_driver =

If you have enabled_backends set then it will only use those driver specs
and ignore all driver related details in the DEFAULT section.

You also probably want to comment (or remove) the default_volume_type
line, unless you plan to create that volume type after the services come

Andrew Kerr
OpenStack QA
Cloud Solutions Group

From:  Amit Das <>
Reply-To:  "OpenStack Development Mailing List (not for usage questions)"
Date:  Thursday, August 14, 2014 at 5:37 AM
To:  OpenStack Development Mailing List <>
Subject:  Re: [openstack-dev] [Devstack] [Cinder] Registering 3rd
party   driver as default

With further debugging, i find that none of the configuration options
present in /etc/cinder/cinder.conf are getting applied.

AmitCloudByte Inc. <>

On Thu, Aug 14, 2014 at 11:40 AM, Amit Das
<> wrote:

Hi folks,

I have been trying to run devstack with my cinder driver as the default
volume_driver but with no luck.

Devstack seems to register the lvm driver as the default always.

I have tried below approaches:

1. directly modifying the /etc/cinder/cinder.conf file
2. creating a driver file @ ./devstack/lib/cinder_plugins/<driver-name>

1. ref -

This is my localrc details:

I run ./ & then FORCE=yes ./

This is the cinder.conf that is generated after running above I
comment out the [lvmdriver-1] section manually
(not sure if this section needs to be commented)

These are portions of c-sch & c-vol logs after restarting them in their
respective screens.

AmitCloudByte Inc. <>

OpenStack-dev mailing list

Reply via email to