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.
This procedure is valid for MOSK clusters that use the deprecated
KaaSCephCluster custom resource (CR) instead of the MiraCeph CR that is
available since MOSK 25.2 as a new Ceph configuration entrypoint. For the
equivalent procedure with the MiraCeph CR, refer to the following section:
Mirantis Ceph Controller simplifies Ceph cluster management by automating LCM
operations. This section describes how to add, remove, or reconfigure Ceph
OSDs.
Manually prepare the required machine devices with LVM2 on the existing
node because BareMetalHostProfile does not support in-place changes.
To add a Ceph OSD to an existing or hot-plugged raw device
If you want to add a Ceph OSD on top of a raw device that already exists
on a node or is hot-plugged, add the required device using the following
guidelines:
You can add a raw device to a node during node deployment.
If a node supports adding devices without node reboot, you can hot plug
a raw device to a node.
If a node does not support adding devices without node reboot, you can
hot plug a raw device during node shutdown. In this case, complete the
following steps:
Enable maintenance mode on the managed cluster.
Turn off the required node.
Attach the required raw device to the node.
Turn on the required node.
Disable maintenance mode on the managed cluster.
Open the KaasCephCluster CR of a managed cluster for editing:
Substitute <managedClusterProjectName> with the corresponding value.
In the nodes.<machineName>.storageDevices or
nodes.<machineName>.storageDeviceFilter section, specify parameters for
a Ceph OSD as required. For description of parameters, see Node parameters.
The example configuration of the nodes section with the new node:
Since MOSK 23.3
nodes:kaas-node-5bgk6:roles:-mon-mgrstorageDevices:-config:# existing itemdeviceClass:hddfullPath:/dev/disk/by-id/scsi-SATA_HGST_HUS724040AL_PN1334PEHN18ZS-config:# new itemdeviceClass:hddfullPath:/dev/disk/by-id/scsi-0ATA_HGST_HUS724040AL_PN1334PEHN1VBC
Before MOSK 23.3
nodes:kaas-node-5bgk6:roles:-mon-mgrstorageDevices:-config:# existing itemdeviceClass:hddname:sdb-config:# new itemdeviceClass:hddname:sdc
Warning
Since MOSK 23.3, Mirantis highly recommends
using the non-wwn by-id symlinks to specify storage devices in the
storageDevices list. For details, see Addressing storage devices prior to MOSK 25.2.
Verify that the Ceph OSD on the specified node is successfully deployed. The
fullClusterInfo section should not contain any issues.
When using the non-recommended Ceph pools replicated.size of
less than 3, Ceph OSD removal cannot be performed. The minimal replica
size equals a rounded up half of the specified replicated.size.
For example, if replicated.size is 2, the minimal replica size is
1, and if replicated.size is 3, then the minimal replica size
is 2. The replica size of 1 allows Ceph having PGs with only one
Ceph OSD in the acting state, which may cause a PG_TOO_DEGRADED
health warning that blocks Ceph OSD removal. Mirantis recommends setting
replicated.size to 3 for each Ceph pool.
Open the KaasCephCluster CR of a managed cluster for editing:
Substitute <managedClusterProjectName> with the corresponding value.
In spec.cephClusterSpec.nodes.<machineName>, remove the required Ceph
OSD specification from the storageDevices list or update
storageDeviceFilter:
The example configuration of the nodes section with the new node:
Since MOSK 23.3
nodes:kaas-node-5bgk6:roles:-mon-mgrstorageDevices:-config:deviceClass:hddfullPath:/dev/disk/by-id/scsi-SATA_HGST_HUS724040AL_PN1334PEHN18ZS-config:# remove the entire item entry from storageDevices listdeviceClass:hddfullPath:/dev/disk/by-id/scsi-0ATA_HGST_HUS724040AL_PN1334PEHN1VBC
Before MOSK 23.3
nodes:kaas-node-5bgk6:roles:-mon-mgrstorageDevices:-config:deviceClass:hddname:sdb-config:# remove the entire item entry from storageDevices listdeviceClass:hddname:sdc
Create a YAML template for the KaaSCephOperationRequest CR. Select from
the following options:
Remove Ceph OSD by device name, by-path symlink, or by-id symlink:
Substitute <managedClusterProjectName> with the corresponding cluster
namespace and <kaasCephClusterName> with the corresponding
KaaSCephCluster name.
Warning
Since MOSK 23.3, Mirantis does not recommend setting device
name or device by-path symlink in the cleanupByDevice field
as these identifiers are not persistent and can change at node boot. Remove
Ceph OSDs with by-id symlinks specified in the path field or use
cleanupByOsdId instead. For details, see Addressing storage devices since MOSK 25.2.
Note
Since MOSK 23.1, cleanupByDevice is not
supported if a device was physically removed from a node. Therefore,
use cleanupByOsdId instead. For details, see
Remove a failed Ceph OSD by Ceph OSD ID.
Before MOSK
23.1, if the storageDevice item was specified with by-id,
specify the path parameter in the cleanupByDevice section
instead of name.
If the storageDevice item was specified with a by-path device
path, specify the path parameter in the cleanupByDevice
section instead of name.