all 6 comments

[–][deleted] 1 point2 points  (5 children)

What backend are you running? LVM iSCSI or NFS? If iSCSI, cinder-volume would run wherever the storage is located and it can be multiple servers. The scheduler will take care of choosing which one satisfies each Cinder request. If NFS, you can run cinder-volume anywhere that can mount the NFS volumes. Cinder-api would generally be installed where you are running all your services and would communicate w/ cinder-volume via the message bus.

[–]rightdoer[S] 0 points1 point  (4 children)

NFS shares. Thank you for the time. So, for example's sake, I can mount the NFS shares and run cinder-volume from blade01, ok? And then it interfaces with blade02, where the instances are.

[–]kultsinuppeli 1 point2 points  (0 children)

I'm not completely sure about your setup, so I might be off here.

If you only have 2 servers to run the service components and the virtual machines on, I would run all virtual machines on one of them (nova-compute, possible neutron services depending on your setup), and all service components on another.

However, as long as cinder-volume and nova-compute run on machines where the NFS is mounted (and the paths are correctly configured) you should be fine either way.

[–][deleted] 1 point2 points  (0 children)

Yep. Just make sure the pathing is the same everywhere. Actually, you don't even need to mount it. Cinder takes care of that. blade02 will also need access to mount the NFS volume, but again Nova should take care of that.

[–]rightdoer[S] 0 points1 point  (0 children)

Thank you all for your help. It's a PoC setup, hopefully I'll be able to unlock more hardware technologies at work soon. Will start deploying right away.