Enable LVM block storage¶
TechPreview
Note
Consider this section as part of Deploy an OpenStack cluster.
This section instructs you on how to configure LVM as a back end for the OpenStack Block Storage service.
Since MOSK 22.4, you can use flexible size
units
throughout bare metal host profiles. For example, you can now use either
sizeGiB: 0.1
or size: 100Mi
when specifying a device size.
Mirantis recommends using only one parameter name type and units throughout
the configuration files. If both sizeGiB
and size
are used,
sizeGiB
is ignored during deployment and the suffix is adjusted
accordingly. For example, 1.5Gi
will be serialized as 1536Mi
. The size
without units is counted in bytes. For example, size: 120
means 120 bytes.
Warning
All data will be wiped during cluster deployment on devices
defined directly or indirectly in the fileSystems
list of
BareMetalHostProfile
. For example:
A raw device partition with a file system on it
A device partition in a volume group with a logical volume that has a file system on it
An mdadm RAID device with a file system on it
An LVM RAID device with a file system on it
Since MOSK 22.3, the wipe
field is always considered true
for these
devices. The false
value is ignored.
Therefore, to prevent data loss, move the necessary data from these file systems to another server beforehand, if required.
To enable LVM block storage:
Open
BareMetalHostProfile
for editing.In the
spec:volumeGroups
section, specify the following data for the OpenStack compute nodes. In the following example, we deploy a Cinder volume with LVM on compute nodes. However, you can use dedicated nodes for this purpose.spec: devices: - device: byName: /dev/nvme0n1 minSize: 30Gi wipe: true partitions: - name: lvm_cinder_vol size: 0 wipe: true volumeGroups: - devices: - partition: lvm_cinder_vol name: cinder-vol logicalVolumes: - name: cinder-fake vg: cinder-vol size: 100Mi fileSystems: - fileSystem: ext4 logicalVolume: cinder-fake mountPoint: /cinder-fake
Note
Due to a limitation, volume groups cannot be created without logical volumes and formatted partitions. Therefore, set the
logicalVolumes:name
,fileSystems:logicalVolume
, andfileSystems:mountPoint
parameters tocinder-fake
.For details about
BareMetalHostProfile
, see Mirantis Container Cloud Operations Guide: Create a custom bare metal host profile.Configure the
OpenStackDeployment
CR to deploy OpenStack with LVM block storage. For example:spec: nodes: openstack-compute-node::enabled: features: cinder: volume: backends: lvm: lvm: volume_group: "cinder-vol"