<p dir="ltr">Thanks John for the detailed information. </p>
<p dir="ltr">I will do the experiments and report the same. </p>
<div class="gmail_quote">On 19 Jan 2015 21:39, "John Griffith" <<a href="mailto:john.griffith@solidfire.com">john.griffith@solidfire.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, Jan 18, 2015 at 11:41 PM, Amit Das <<a href="mailto:amit.das@cloudbyte.com">amit.das@cloudbyte.com</a>> wrote:<br>
> Hi John,<br>
><br>
>><br>
>> Otherwise you can move to multibackend but you will need to update the<br>
>> hosts column on your existing volumes.<br>
><br>
><br>
> For above statement, did you mean a unique backend on separate volume nodes<br>
> ?<br>
><br>
> Will there be any issues, if the enabled_backends are used with each backend<br>
> tied to particular volume type. Now this configuration is repeated for all<br>
> volume nodes. Do we need to be concerned about the host entry ?<br>
><br>
><br>
> Regards,<br>
> Amit<br>
> CloudByte Inc.<br>
><br>
> On Mon, Jan 19, 2015 at 4:14 AM, John Griffith <<a href="mailto:john.griffith@solidfire.com">john.griffith@solidfire.com</a>><br>
> wrote:<br>
>><br>
>><br>
>> On Jan 16, 2015 9:03 PM, "mad Engineer" <<a href="mailto:themadengin33r@gmail.com">themadengin33r@gmail.com</a>> wrote:<br>
>> ><br>
>> > Hello All,<br>
>> > i am working on integrating VNX with cinder,i have plan<br>
>> > to add another NFS storage in the future,without removing VNX.<br>
>> ><br>
>> > Can i add another backend while first backend is running without<br>
>> > causing problem to running volumes.<br>
>> > I heard that multiple backend is supported,<br>
>> ><br>
>> > thanks for any help<br>
>> ><br>
>> > _______________________________________________<br>
>> > Mailing list:<br>
>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
>> > Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>> > Unsubscribe :<br>
>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
>><br>
>> So as long as you used the "enabled backend" format in your existing<br>
>> config you "should" be able to just add another backend without impacting<br>
>> your existing setup (I've never tried this with NFS/VNX myself though).<br>
>><br>
>> If you're not using the enabled backends directive you can deploy a new<br>
>> cinder - volume node and just add your new driver that way.<br>
>><br>
>> Otherwise you can move to multibackend but you will need to update the<br>
>> hosts column on your existing volumes.<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Mailing list:<br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
>> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>> Unsubscribe :<br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
>><br>
><br>
<br>
Hi Amit,<br>
<br>
My point was that the way multi-backend works is by the addition of<br>
the "enabled_backends" parameter in the cinder.conf file, along with a<br>
driver section:<br>
<br>
enabled_backends = lvm1,lvm2<br>
[lvm1]<br>
<driver settings><br>
[lvm2]<br>
<driver settings><br>
<br>
This will cause your host entry to be of the form:<br>
<cinder-vol-node-name>@<backend-name><br>
<br>
In this scenario you can simply add another entry for enabled_backends<br>
and it's corresponding driver info entry.<br>
<br>
If you do NOT have multi backend setup your host entry will just be:<br>
<cinder-vol-node-name> and it's a bit more difficult to convert to<br>
multi-backend. You have two options:<br>
1. Just deploy another cinder-volume node (skip multi-backend)<br>
2. Convert existing setup to multi-backend (this will require<br>
modification/update of the host entry of your existing volumes)<br>
<br>
This all might be a bit more clear if you try it yourself in a<br>
devstack deployment. Give us a shout on IRC at openstack-cinder if<br>
you get hung up.<br>
<br>
Thanks,<br>
John<br>
</blockquote></div>