<div dir="ltr"><div dir="ltr">Hello Sean<div><br></div><div>Thanks much for the detailed response.</div><div><br></div><div>I am still unclear on below points </div><div><br></div><div> if you have cross az attach disable in nova and you want all<br>
type/backend to be accessible in all AZ you need to deploy a instance of<br>
the cinder volume driver for each of the types in each az.</div><div><br></div><div> "deploy a instance of<br></div><div>
the cinder volume driver for each of the types in each az"
<<<< How can i achieve above mentioned thing
<br>
<br>
i don't know if that answers your question or not but volume types are<br>
the way to request a specific backend at the api level. <<< i see volume type option while creating volume .. <br></div><div>But when I am trying to launch an instance I don't see that parameter in Horizon .. may be in the command line we have (not sure though) .</div><div>Is this something that needs to be handled at AZ level ?</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 14, 2020 at 7:29 PM Sean Mooney <<a href="mailto:smooney@redhat.com">smooney@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, 2020-10-14 at 18:38 +0530, Deepa KR wrote:<br>
> Hi All<br>
> <br>
> Good Day<br>
> <br>
> From documentation we are able to understand that we can configure<br>
> multiple<br>
> backends for cinder (Ceph ,External Storage device or NFS etc)<br>
> Is there any way we can choose the backend while instance launching<br>
> .Say<br>
<br>
> instance1 backend should be from an external storage device like EMC <br>
> and<br>
> instance2 to launch and have backend volume from ceph<br>
kind of you can use volume types to do this indrectly.<br>
end users shoudl generally not be aware if its ceph or an emc san you<br>
less you name the volumens tyeps "cpeh" and "emc" but that is a<br>
operator choice. you can map the volume type to specific backend using<br>
there config file.<br>
<br>
> .Can this be achieved<br>
> using cinder availability zone implementation or any other way?<br>
> <br>
> I have gone through below link (*section Configure Block Storage<br>
> scheduler<br>
> multi back end)*<br>
> <br>
> <br>
> <a href="https://docs.openstack.org/cinder/latest/admin/blockstorage-multi-backend.html" rel="noreferrer" target="_blank">https://docs.openstack.org/cinder/latest/admin/blockstorage-multi-backend.html</a><br>
<br>
well that basically covers what you have to do<br>
<br>
your cinder config for lvm emc and ceph might look like this<br>
<br>
<br>
[DEFAULT]<br>
enabled_backends=lvm,emc,ceph<br>
<br>
[lvm]<br>
volume_group = cinder-volume-1<br>
volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver<br>
<br>
[emc]<br>
use_multipath_for_image_xfer = true<br>
volume_driver = cinder.volume.drivers.emc.emc_smis_fc.EMCSMISFCDriver<br>
volume_backend_name = emcfc<br>
<br>
[ceph]<br>
volume_driver = cinder.volume.drivers.rbd.RBDDriver<br>
volume_backend_name = ceph<br>
rbd_pool = volumes<br>
rbd_ceph_conf = /etc/ceph/ceph.conf<br>
rbd_flatten_volume_from_snapshot = false<br>
rbd_max_clone_depth = 5<br>
rbd_store_chunk_size = 4<br>
rados_connect_timeout = -1<br>
<br>
or you might have 3 diffent config one for each<br>
<br>
you then create 3 different volume types and assocatie each with a<br>
backend<br>
<br>
openstack --os-username admin --os-tenant-name admin volume type create<br>
lvm<br>
openstack --os-username admin --os-tenant-name admin volume type create<br>
emc<br>
openstack --os-username admin --os-tenant-name admin volume type create<br>
ceph<br>
<br>
openstack --os-username admin --os-tenant-name admin volume type set<br>
lvm --property volume_backend_name=lvm<br>
openstack --os-username admin --os-tenant-name admin volume type set<br>
emc --property volume_backend_name=emc<br>
openstack --os-username admin --os-tenant-name admin volume type set<br>
ceph --property volume_backend_name=ceph<br>
<br>
<br>
then you can create volumes with those types<br>
<br>
openstack volume create --size 1 --type lvm my_lvm_volume<br>
openstack volume create --size 1 --type ceph my_ceph_volume<br>
<br>
and boot a server with them.<br>
<br>
openstack server create --volume my_lvm_volume --volume my_ceph_volume<br>
...<br>
<br>
<br>
if you have cross az attach disabel in nova and you want all<br>
type/backend to be accesable in all AZ you need to deploy a instance of<br>
the cinder volume driver for each of the tyeps in each az.<br>
<br>
i dont know if that answers your question or not but volume types are<br>
the way to requst a specific backend at the api level.<br>
<br>
> <br>
> Suggestions please ..<br>
> <br>
> Regards,<br>
> Deepa K R<br>
<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><p style="margin:0in 0in 0.0001pt"><br>Regards,</p><p style="margin:0in 0in 0.0001pt"><font color="#ff0000">Deepa K R</font><font color="#666666"> | DevOps Team Lead</font></p><span><p style="margin:0in 0in 0.0001pt"><font color="#666666"><br></font></p><p style="margin:0in 0in 0.0001pt"><font size="4"></font><img src="cid:ii_144d3e1003a21d10" width="200" height="63"><br></p><p style="margin:0in 0in 0.0001pt"><span style="color:rgb(0,0,0);font-family:Arial;font-size:x-small;white-space:pre-wrap">USA | UAE | INDIA | AUSTRALIA</span><br></p><p style="margin:0in 0in 0.0001pt"><br></p><p class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-IN"></span></p></span><p style="margin:0in 0in 0.0001pt"><img src="cid:ii_14192b6d31f4f112"></p></div></div></div></div></div>