Open Stack

Cecilia,

There isn't really a recommended configuration for what you are trying 
to do.  It really comes down to what works best for you. If Cinder has 
been performing well enough for you running on the Controller then I 
personally wouldn't change that.

If you update your configuration to add the HPMSA backend it will start 
a new volume process for handling management of that backend.  So, it 
will be a separate process from the one that is currently managing the 
NFS storage.  Otherwise, you can configure the volume process to run on 
any other baremetal server for the HPMSA management.  That, however, 
seems overly complicated for your use case.

Hope this helps.

Jay

On 12/20/2018 7:45 AM, Cecilia Di Maulo wrote:
> Dear all,
>
> I currently have a NFS backend for Cinder and I would like to add an 
> iSCSI (hpmsa) backend. However I was wondering where should the cinder 
> services run? For now cinder-api.service and cinder-scheduler.service 
> run in a lxc while cinder-volume.service runs in bare metal on the 
> controllers.
>
> I also would like to separate as much as possible the 2 backend types 
> to be able to remove 'easily' my NFS backend once the other one has 
> proved it really works.
>
> I was thinking to have the services related to the NFS backend in a 
> lxc and the services related to the HPMSA backend on metal. Is this 
> even possible? How should I do it? Should I name 2 different services 
> in the container_skel or..?
>
> Thank you for your help,
>
> Best Regards,
>
> Cecilia