To answer your question, no, it is not required to be unique per MySQL deployment. So the way this works is that SERVICE_NAME creates a pool on which the rbd-name (which is used to create the image) is created. So for example I deploy 3 mysql units against 1 ceph for HA (juju deploy mysql -n) they all need access to the same image (hence the same pool).
Now, however, if I deploy X mysql services (with various units) as mysqlX, mysqlY, etc (juju deploy mysql mysqlX && juju deploy mysql mysqlY) against 1 ceph, each mysqlX service will have to access to a corresponding 'pool' where the image rbd-name is created. So there would be 2 pools of images 'mysqlx', 'mysqly' each with an image called 'mysql1'.
Hi Marco,
To answer your question, no, it is not required to be unique per MySQL deployment. So the way this works is that SERVICE_NAME creates a pool on which the rbd-name (which is used to create the image) is created. So for example I deploy 3 mysql units against 1 ceph for HA (juju deploy mysql -n) they all need access to the same image (hence the same pool).
Now, however, if I deploy X mysql services (with various units) as mysqlX, mysqlY, etc (juju deploy mysql mysqlX && juju deploy mysql mysqlY) against 1 ceph, each mysqlX service will have to access to a corresponding 'pool' where the image rbd-name is created. So there would be 2 pools of images 'mysqlx', 'mysqly' each with an image called 'mysql1'.
Hope this helps.
Regards.