@David I think the complexity is to be able to offer a simple interface / API way for users to configure multiple storages. Maybe through smapi v3.
In any case we currently only support one storage pool, the sm driver would have to be reworked to support several. It also probably requires visibility from XOA's point of view. Lots of points to discuss. I will create a card on our internal Kanban.

Regarding multiple XOSTOR SRs, we must:

Add a way to move the controller volume on a specific storage pool. Ensure the controller it is still accessible for remaining SRs despite the destruction of an SR. Use a lock mechanism to protect the LINSTOR env.

@olivierlambert Thanks for the clarification, it is definitely from sources. Apologies I will try to remember!

I'll patch my system a little later today.

Edit: Patched to Xen Orchestra, commit 6953e - All good.

Thanks, really appreciate the prompt fix!

Which is exactly the right behavior! Perfect 🙂 Thanks for the feedback.