1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Files
openshift-docs/modules/lvms-reference-file.adoc
John Wilkins 2f54904445 Added optionalPaths to deviceSelector.
Signed-off-by: John Wilkins <jowilkin@redhat.com>
2023-09-26 21:41:24 +00:00

75 lines
2.5 KiB
Plaintext

// Module included in the following assemblies:
//
// storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc
:_content-type: REFERENCE
[id="lvms-reference-file_{context}"]
= {lvms} reference YAML file
The sample `LVMCluster` custom resource (CR) describes all the fields in the YAML file.
.Example LVMCluster CR
[source,yaml]
----
apiVersion: lvm.topolvm.io/v1alpha1
kind: LVMCluster
metadata:
name: my-lvmcluster
spec:
tolerations:
- effect: NoSchedule
key: xyz
operator: Equal
value: "true"
storage:
deviceClasses: <1>
- name: vg1 <2>
default: true
nodeSelector: <3>
nodeSelectorTerms: <4>
- matchExpressions:
- key: mykey
operator: In
values:
- ssd
deviceSelector: <5>
paths:
- /dev/disk/by-path/pci-0000:87:00.0-nvme-1
- /dev/disk/by-path/pci-0000:88:00.0-nvme-1
optionalPaths:
- /dev/disk/by-path/pci-0000:89:00.0-nvme-1
- /dev/disk/by-path/pci-0000:90:00.0-nvme-1
thinPoolConfig: <6>
name: thin-pool-1 <7>
sizePercent: 90 <8>
overprovisionRatio: 10 <9>
status:
deviceClassStatuses: <10>
- name: vg1
nodeStatus: <11>
- devices: <12>
- /dev/nvme0n1
- /dev/nvme1n1
- /dev/nvme2n1
node: my-node.example.com <13>
status: Ready <14>
ready: true <15>
state: Ready <16>
----
<1> The LVM volume groups to be created on the cluster. Currently, only a single `deviceClass` is supported.
<2> The name of the LVM volume group to be created on the nodes.
<3> The nodes on which to create the LVM volume group. If the field is empty, all nodes are considered.
<4> A list of node selector requirements.
<5> A list of device paths which is used to create the LVM volume group. If this field is empty, all unused disks on the node will be used.
<6> The LVM thin pool configuration.
<7> The name of the thin pool to be created in the LVM volume group.
<8> The percentage of remaining space in the LVM volume group that should be used for creating the thin pool.
<9> The factor by which additional storage can be provisioned compared to the available storage in the thin pool.
<10> The status of the `deviceClass`.
<11> The status of the LVM volume group on each node.
<12> The list of devices used to create the LVM volume group.
<13> The node on which the `deviceClass` was created.
<14> The status of the LVM volume group on the node.
<15> This field is deprecated.
<16> The status of the `LVMCluster`.