<div dir="ltr"><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">Thanks a lot.</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">
This worked out like a charm.</div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><font style="background-color:rgb(255,255,255)" color="#000000" face="trebuchet ms, sans-serif">Regards,</font></div>
<font style="background-color:rgb(255,255,255)" color="#000000" face="trebuchet ms, sans-serif">Amit</font><div><a href="http://www.cloudbyte.com/" target="_blank"><font style="background-color:rgb(255,255,255)" color="#0000ff" face="trebuchet ms, sans-serif"><i>CloudByte Inc.</i></font></a></div>
</div></div>
<br><br><div class="gmail_quote">On Thu, Aug 14, 2014 at 7:02 PM, Kerr, Andrew <span dir="ltr"><<a href="mailto:Andrew.Kerr@netapp.com" target="_blank">Andrew.Kerr@netapp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You either need to comment out the enabled_backends line, or you'll want<br>
to put something similar to this in your cinder.conf file:<br>
<br>
[DEFAULT]<br>
...<br>
enabled_backends = cloudbyte<br>
...<br>
[cloudbyte]<br>
volume_driver = volume_driver =<br>
cinder.volume.drivers.cloudbyte.cloudbyte.ElasticenterISCSIDriver<br>
SAN_IP=20.10.22.245<br>
CB_APIKEY=masQwghrmPOVIqbjyyWKQdg4z4bP2sNZ13fRQyUMwm453PUiYB-xyRSMBDoZeMj6R<br>
0-XU9DCscxMbe3AhleDyQ<br>
CB_ACCOUNT_NAME=acc1<br>
TSM_NAME=openstacktsm<br>
<br>
<br>
<br>
If you have enabled_backends set then it will only use those driver specs<br>
and ignore all driver related details in the DEFAULT section.<br>
<br>
You also probably want to comment (or remove) the default_volume_type<br>
line, unless you plan to create that volume type after the services come<br>
up.<br>
<br>
Andrew Kerr<br>
OpenStack QA<br>
Cloud Solutions Group<br>
NetApp<br>
<br>
<br>
From: Amit Das <<a href="mailto:amit.das@cloudbyte.com">amit.das@cloudbyte.com</a>><br>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Date: Thursday, August 14, 2014 at 5:37 AM<br>
To: OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Devstack] [Cinder] Registering 3rd<br>
party driver as default<br>
<div class=""><br>
<br>
With further debugging, i find that none of the configuration options<br>
present in /etc/cinder/cinder.conf are getting applied.<br>
<br>
<br>
Regards,<br>
</div>AmitCloudByte Inc. <<a href="http://www.cloudbyte.com/" target="_blank">http://www.cloudbyte.com/</a>><br>
<div class=""><br>
<br>
<br>
<br>
On Thu, Aug 14, 2014 at 11:40 AM, Amit Das<br>
<<a href="mailto:amit.das@cloudbyte.com">amit.das@cloudbyte.com</a>> wrote:<br>
<br>
Hi folks,<br>
<br>
I have been trying to run devstack with my cinder driver as the default<br>
volume_driver but with no luck.<br>
<br>
Devstack seems to register the lvm driver as the default always.<br>
<br>
I have tried below approaches:<br>
<br>
</div>1. directly modifying the /etc/cinder/cinder.conf file<br>
2. creating a driver file @ ./devstack/lib/cinder_plugins/<driver-name><br>
<br>
1. ref - <a href="https://review.openstack.org/#/c/68726/" target="_blank">https://review.openstack.org/#/c/68726/</a><br>
<div class=""><br>
<br>
<br>
<br>
<br>
<br>
This is my localrc details:<br>
<a href="http://paste.openstack.org/show/94822/" target="_blank">http://paste.openstack.org/show/94822/</a><br>
<br>
<br>
I run ./unstack.sh & then FORCE=yes ./stack.sh<br>
<br>
This is the cinder.conf that is generated after running above stack.sh. I<br>
comment out the [lvmdriver-1] section manually<br>
(not sure if this section needs to be commented)<br>
<br>
<a href="http://paste.openstack.org/show/94841/" target="_blank">http://paste.openstack.org/show/94841/</a><br>
<br>
<br>
These are portions of c-sch & c-vol logs after restarting them in their<br>
respective screens.<br>
<br>
<a href="http://paste.openstack.org/show/94842/" target="_blank">http://paste.openstack.org/show/94842/</a><br>
<br>
<br>
<br>
Regards,<br>
</div>AmitCloudByte Inc. <<a href="http://www.cloudbyte.com/" target="_blank">http://www.cloudbyte.com/</a>><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div>