<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>You configure an LVM volume group for each Cinder backend. A
CInder volume on that backend corresponds to an LVM volume in that
volume group. The LVM volume is exposed as an iSCSI target,
usually via LIO, but I believe this is configurable. The compute
node uses <i>iscsiadm </i>to import that volume as a SCSI device
and connects that device to the VM.</p>
<p>I don't know if this is documented anywhere, but it's easy and
fun to explore. On the storage node, use LVM commands to look into
volume groups and volumes, and the <i>tgtadm </i>command to
check targets. On the compute node, list all SCSI disks, use <i>iscsiadm
-m session </i>to check iSCSI sessions, and use <i>virsh
domblklist </i>and <i>virsh edit </i>(assuming your
hypervisor is libvirt-controlled) to confirm that the iSCSI LUN is
connected to the VM.</p>
On 10/26/2018 10:03 PM, Tushar Tyagi wrote:<br>
<blockquote type="cite"
cite="mid:1540559010.198597.1555525240.5ABEA474@webmail.messagingengine.com">
<pre wrap="">I am using Rocky release and configuring for NVMe backend with LVM. Can you please tell me how this one might flow, or redirect me to the documentation?
I have not been able to found much documentation regarding this.
</pre>
</blockquote>
<br>
</body>
</html>