<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 15, 2015 at 8:53 AM, Eduard Matei <span dir="ltr"><<a href="mailto:eduard.matei@cloudfounders.com" target="_blank">eduard.matei@cloudfounders.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">Hi,
</div><div class="gmail_extra"><br></div><div class="gmail_extra">Let me see if i got this:</div><div class="gmail_extra">- running 3 (multiple) c-vols won't automatically give you failover </div></div></blockquote><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline">correct</div></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline"></div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">- each c-vol is "master" of a certain number of volumes</div></div></blockquote><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline">yes</div></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline"></div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">-- if the c-vol is "down" then those volumes cannot be managed by another c-vol</div></div></blockquote><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline">By default no, but you can configure an HA setup of multiple c-vol services. There are a number of folks doing this in production and there's probably better documentation on how to achieve this, but this gives a descent enough start:</div></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline"><a href="http://docs.openstack.org/high-availability-guide/content/s-cinder-api.html">http://docs.openstack.org/high-availability-guide/content/s-cinder-api.html</a></div></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline"></div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br></div><div class="gmail_extra">What i'm trying to achieve is making sure ANY volume is managed (manageable) by WHICHEVER c-vol is running (and gets the call first) - sort of A/A - so this means i need to look into Pacemaker and virtual-ips, or i should try first the "same name".</div></div></blockquote><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline">Yes, I gathered... and to do that you need to do something like name the backends the same and use a VIP in from of them.</div></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline"></div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Eduard</div><div class="gmail_extra"><br></div><div class="gmail_extra">PS. @Michal: <span style="font-size:12.8px">Where are volumes physically in case of your driver? <- similar to ceph, on a distributed object storage service (whose disks can be anywhere even on the same compute host)</span></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>