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 Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Comparison of KaaSCephCluster and MiraCeph-related specifications

MiraCeph is available since MOSK 25.2

This section describes all differences and matches between KaaSCephCluster and MiraCeph custom resources (CRs). Since MOSK 25.2, KaaSCephCluster is deprecated and all Ceph management will be moved to MiraCeph in one of upcoming releases. The following Ceph CRs of the MOSK cluster will be used instead: MiraCeph, MiraCephHealth, MiraCephSecret, and MiraCephMaintenance.

Since MOSK 25.2, the KaaSCephOperationRequest CR of the management cluster is also deprecated and replaced by the CephOsdRemoveRequest CR of the MOSK cluster. For details on how to use CephOsdRemoveRequest, see Automated Ceph LCM.

KaaSCephCluster and MiraCeph comparison details

MiraCeph is the main Ceph cluster management CR on a MOSK cluster that allows configuring a Ceph cluster on day-1 and day-2 operations. The following sections of KaaSCephCluster match the MiraCeph fields:

• KaaSCephCluster spec.cephClusterSpec generally matches MiraCeph spec except the following options:

  • The nodes section in MiraCeph is a list of key-value mappings instead of the map of mappings presented in KaaSCephCluster. Each list item is a node or node group specification where name stands for a MOSK cluster node name instead of a Machine name, which is used in KaaSCephCluster. The devices list is the same as storageDevices of KaaSCephCluster and node groups cab be configured with the nodeGroup list of node names. For the full list of parameters, see Node parameters.

    Difference examples:

    KaaSCephCluster nodes and nodeGroups sections

    kind: KaaSCephCluster
    ...
    spec:
      cephClusterSpec:
        ...
        nodes:
          machine-name-1:
            crush:
              rack: rack-1
            roles: ["mds"]
            storageDevices:
            - fullPath: /dev/disk/by-id/something
              config:
                deviceClass: nvme
                osdsPerDevice: "4"
        nodeGroups:
          group-1:
            spec:
              crush:
                rack: rack-1
              roles: ["mds"]
              storageDevices:
              - name: nvmeXnY
                config:
                  deviceClass: nvme
                  osdsPerDevice: "4"
            nodes:
            - machine-name-2
            - machine-name-3
    

    MiraCeph nodes section

    kind: MiraCeph
    ...
    spec:
      ...
      nodes:
      - name: node-name-1
        crush:
          rack: rack-1
        roles: ["mds"]
        devices:
        - fullPath: /dev/disk/by-id/something
          config:
            deviceClass: nvme
            osdsPerDevice: "4"
      - name: group-1
        nodeGroup:
        - node-name-2
        - node-name-3
        crush:
          rack: rack-1
        roles: ["mds"]
        devices:
        - name: nvmeXnY
          config:
            deviceClass: nvme
            osdsPerDevice: "4"
    

  • The MiraCeph network section must have publicNet and clusterNet parameters explicitly defined.

    Since KaaSCephCluster was located on a management cluster, these parameters could be left empty because a management cluster has access to IPAM settings that allow defining which subnets to use. And since MiraCeph is a MOSK cluster resource, it has no access to a management cluster data. Therefore, subnets must be explicitly defined in the network section. For details, see General parameters.

• The status.miraCephInfo section in KaaSCephCluster fully matches status in MiraCeph.

KaaSCephCluster and MiraCephHealth comparison details

MiraCephHealth contains full report about Ceph cluster health and main information. Its sections match the following KaaSCephCluster fields:

• The status.fullClusterInfo of KaaSCephCluster matches status.fullClusterStatus of MiraCephHealth except the following item:

  • The fullClusterInfo.cephDetails.deviceMappingMapRef referenced object KaaSCephExtraInfo data of KaaSCephCluster is placed in the fullClusterStatus.cephDetails.deviceMapping section of MiraCephHealth.

• The status.shortClusterInfo parameters of KaaSCephCluster have the following matches in the status section of MiraCephHealth:

  lastCheck lastUpdate miraCephGeneration

  state messages

  For example, status.shortClusterInfo.lastCheck in KaaSCephCluster matches status.lastCheck in MiraCephHealth.

KaaSCephCluster and MiraCephSecret comparison details

MiraCephSecret contains references to all credential secrets of custom Ceph clients and Ceph Object Storage users. The status.miraCephSecretsInfo section of KaaSCephCluster fully matches the status section of MiraCephSecret.

KaaSCephCluster and MiraCephMaintenance comparison details

MiraCephMaintenance contains information about current maintenance. The status.miraCephMaintenanceInfo section of KaaSCephCluster fully matches the status section of MiraCephMaintenance.