Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly MCC). This means everything you need is in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Obtain a by-id symlink of a storage device¶

Warning

This procedure is valid for MOSK clusters that use the MiraCeph custom resource (CR), which is available since MOSK 25.2 to replace the deprecated KaaSCephCluster. For the equivalent procedure with the KaaSCephCluster CR, refer to the following section:

Obtain a by-id symlink of a storage device

You can start using a storage device only after a corresponding Machine becomes ready and accessible. Thus, MiraCeph can be created only after all machines receive the status.providerStatus.hardware.storage configuration containing all required device by-id symlinks.

To obtain a device by-id symlink:

Verify that the Machine is Ready:
```
kubectl -n <moskClusterProject> get machine <machineName> -o jsonpath='{.status.phase}{"\n"}'
```
Substitute <moskClusterProject> with the cluster namespace and <machineName> with the machine name.

Obtain storage details for the Machine:

kubectl -n <moskClusterProject> get machine <machineName> -o yaml

In the status.providerStatus.hardware.storage section, obtain the item from the byIDs list that contains serialNumber and does not contain wwn as a bus ID.

In the example above, for the disk with the /dev/sdc name, you can use the /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_2e52abb48862dbdc symlink as a persistent identifier of the storage device because it contains the 2e52abb48862dbdc serial number and does not contain wwn.

Note

Do not rely on the byID field only. This field may contain a /dev/disk/by-id/wwn symlink that cannot be considered a persistent identifier of a storage device.