[Openstack] [Cinder] Loading cinder.conf

John Griffith john.griffith at solidfire.com
Tue Jul 16 18:55:14 UTC 2013


On Tue, Jul 16, 2013 at 12:41 AM, zan tosh <ztosh71 at gmail.com> wrote:

> Thanks for all your responses. I didn't realize that stack.sh actually
> copies the cinder.conf.sample instead of cinder.conf to /etc/cinder every
> time it runs. So, it was overwriting my entries. I fixed it by making
> changes to the script. The issue is resolved.
>
>
> On Mon, Jul 15, 2013 at 4:54 PM, Unmesh Gurjar <unmesh.gurjar at gmail.com>wrote:
>
>> Hi,
>>
>> AFAIK, there are no additional changes required (other than restarting
>> the service so that it loads the new conf settings). Assuming you have done
>> that, can you check what is the 'volume_driver' from the service start up
>> logs?
>>
>>
>> ~Unmesh.
>>
>> On Mon, Jul 15, 2013 at 10:44 AM, zan tosh <ztosh71 at gmail.com> wrote:
>>
>>> Ray
>>>
>>> I am wondering why I see the default driver even after I changed the
>>> entry in cinder.conf. I un-commented the line for volume_driver and changed
>>> the driver name. I tried to print volume driver in the __init__ and I see
>>> it still pointing to LVMISCSIDriver. It seems I am missing something
>>> and its not loading values from cinder.conf.
>>>
>>> ~z
>>>
>>>
>>> On Mon, Jul 15, 2013 at 10:33 AM, Ray Sun <xiaoquqi at gmail.com> wrote:
>>>
>>>> Yes, that's the default driver. See cinder/volume/manager.py
>>>> volume_manager_opts = [
>>>>     cfg.StrOpt('volume_driver',
>>>>                default='cinder.volume.drivers.lvm.LVMISCSIDriver',
>>>>                help='Driver to use for volume creation'),
>>>> ]
>>>>
>>>> Best Regards
>>>> -- Ray
>>>>
>>>>
>>>> On Mon, Jul 15, 2013 at 12:51 PM, zan tosh <ztosh71 at gmail.com> wrote:
>>>>
>>>>> I use devstack (Grizzly/stable). I have been trying to use a different
>>>>> volume driver by muncommenting and modifying the below line in cinder.conf
>>>>> under etc/cinder
>>>>> # Driver to use for volume creation (string value)
>>>>> #volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
>>>>>
>>>>> But when VolumeManager is loaded I see it still refers to the default
>>>>> LVMISCSIDriver. Is there any other change to load cinder.conf?
>>>>>
>>>>> Any suggestions?
>>>>>
>>>>> Tahnks
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~openstack
>>>>> Post to     : openstack at lists.launchpad.net
>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack at lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Yes, devstack will overwrite each time your run stack.sh.  You can also
modify your cinder.conf file and then just resart the cinder-volume service
(use screen -x to access the service).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130716/8cc11340/attachment.html>


More information about the Openstack mailing list