Re: [Openstack] IO flow on multi-node setup

2018-10-26 Thread Bernd Bausch
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 /iscsiadm /to import that volume as

Re: [Openstack] IO flow on multi-node setup

2018-10-26 Thread Tushar Tyagi
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. -- Tushar Tyagi t...@fastmail.com On Fri, Oct 26, 2018, at 17:48, Bernd

Re: [Openstack] IO flow on multi-node setup

2018-10-26 Thread Bernd Bausch
Volume I/O won't flow through the controller. The LVM reference driver, for example, sets up an iSCSI target on the storage node, which the compute node then imports. The NFS driver has the compute node mount the exported filesystem. Depending on the driver, I/O may even flow directly between an

[Openstack] IO flow on multi-node setup

2018-10-26 Thread Tushar Tyagi
Hello, I have a requirement to create a multi node setup with Controller, Compute and Storage nodes on different machines. In case I create a virtual machine on the compute node, it's going to be provisioned by the Controller node and the storage is going to be provided by the Storage node.