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 unsupported KaaSCephCluster resource. And MiraCeph will be automatically migrated to CephDeployment in MOSK 26.1. For details, see Deprecation Notes: KaaSCephCluster API on management clusters.

For the equivalent procedure with the unsupported 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 either serialNumber or 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.

No results

An error occurred

Obtain a by-id symlink of a storage device¶