Here is how share instance requested with partition_reference='RU1' looks on slapproxy:

    {'_': {'ru_type': 'lopcomm', 'ru_link_type': 'cpri', 'mac_addr': 'XXX', 'cpri_link': {'sdr_dev': 2, 'sfp_port': 0, 'mult': 8, 'mapping': 'standard', 'rx_delay': 10, 'tx_delay': 11, 'tx_dbm': 50}, 'n_antenna_dl': 2, 'n_antenna_ul': 1, 'tx_gain': -21, 'rx_gain': -22}, 'slap_software_type': 'enb', 'slave_reference': '_RU1', 'slave_title': '_RU1'}

    (note both slave_reference and slave_title relate to partition_reference used in request)

and here is how another shared instance requested the same way looks on slapos master:

    {'_': {'ru_type': 'lopcomm', 'ru_link_type': 'cpri', 'cpri_link': {'sdr_dev': 0, 'sfp_port': 1, 'mult': 4, 'mapping': 'hw', 'rx_delay': 25.11, 'tx_delay': 14.71, 'tx_dbm': 63}, 'n_antenna_dl': 1, 'n_antenna_ul': 1, 'tx_gain': -20, 'rx_gain': -20}, 'connection-parameter-hash': '4f53cda18c2baa0c0354bb5f9a3ecbe5ed12ab4d8e11ba873c2f11161202b945', 'slap_software_type': 'enb', 'slave_reference': 'SOFTINST-218663', 'slave_title': 'RU1', 'timestamp': 1697712836}

note that slave_reference is now unrelated and is some identifier slapos master picked up automatically.

The trace of the original reference is left only in slave_title.

Rafael confirmed, that for instances requested by user, that slave_title cannot
be duplicate for two different instances (because request with
partition_reference=X will adjust another instance previouslt requested with
same partition_reference=X instead of creating another one).

However for instances requested by partitions - it is possible to have two
sepearate shared instances requested with the same partition_reference=X and
having the same slave_title=X. Those instances will live in different instance
trees though.