Comment 2 for bug 2055403

Hi Edward,
thanks for your comment.
But the problem happens for ephemeral storage only (and only if you want to use Ceph for ephemeral disks).

As you correctly said, nova-compute has another relation for cinder-ceph:
cinder-ceph:ceph-access nova-compute:ceph-access

and it works without any problem (tested in my lab environment right now). More specifically, "it works" means the following:

- you have 2 independent Ceph servers and both are used for Cinder volumes. It's possible through the cinder-ceph charm (deployed 2 times with different names)

So, just to summarize, I think the problem is:

If you have 2 independent Ceph storages, you must choose which one you want to use for ephemeral disks (unless you deploy 2 different nova-compute applications). You can use both servers for Cinder volumes.

In my opinion, the nova-compute charm should avoid adding multiple relations like the following:
ceph-mon:client nova-compute:ceph
ceph-mon-d2:client nova-compute:ceph

and that's the bug I'm focused on. The nova-compute charm should notice that a ceph-mon:client relation is already applied and rejecting other relations of the same type with other ceph-mon Juju applications

Regards,
Marco