mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
be8a6929c7
ref config updates Adding generated YAML + modules from the RDS Reorganizing TOC Adding latest RDS updates RDS doc updates RDS YAML updates Shanes review latest updates + new components overview diagram David J's review comments CCS attributes update Ian's review comments adding Hari's deviations update updating 4.14 link URLs Generalizes scope and deviation topics for RAN and Core updates for RDS prod version update deviations wording Updating deviation and scope topics consolidate dev and scope topics + intro Adding link to ztp-site-generate procedure typo final changes for RDS typos Ian's comments update for RDS terminology remove core CRs note add GH core CRs link
57 lines
1.6 KiB
Plaintext
57 lines
1.6 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * telco_ref_design_specs/ran/telco-ran-ref-du-components.adoc
|
|
|
|
:_mod-docs-content-type: REFERENCE
|
|
[id="telco-ran-lvms-operator_{context}"]
|
|
= LVMS Operator
|
|
|
|
New in this release::
|
|
* No reference design updates in this release
|
|
|
|
New in this release::
|
|
* Simplified LVMS `deviceSelector` logic
|
|
|
|
* LVM Storage with `ext4` and `PV` resources
|
|
|
|
[NOTE]
|
|
====
|
|
LVMS Operator is an optional component.
|
|
====
|
|
|
|
Description::
|
|
The LVMS Operator provides dynamic provisioning of block and file storage.
|
|
The LVMS Operator creates logical volumes from local devices that can be used as `PVC` resources by applications.
|
|
Volume expansion and snapshots are also possible.
|
|
+
|
|
The following example configuration creates a `vg1` volume group that leverages all available disks on the node except the installation disk:
|
|
+
|
|
.StorageLVMCluster.yaml
|
|
[source,yaml]
|
|
----
|
|
apiVersion: lvm.topolvm.io/v1alpha1
|
|
kind: LVMCluster
|
|
metadata:
|
|
name: storage-lvmcluster
|
|
namespace: openshift-storage
|
|
annotations:
|
|
ran.openshift.io/ztp-deploy-wave: "10"
|
|
spec: {}
|
|
storage:
|
|
deviceClasses:
|
|
- name: vg1
|
|
thinPoolConfig:
|
|
name: thin-pool-1
|
|
sizePercent: 90
|
|
overprovisionRatio: 10
|
|
----
|
|
|
|
Limits and requirements::
|
|
* In {sno} clusters, persistent storage must be provided by either LVMS or Local Storage, not both.
|
|
|
|
Engineering considerations::
|
|
* The LVMS Operator is not the reference storage solution for the DU use case.
|
|
If you require LVMS Operator for application workloads, the resource use is accounted for against the application cores.
|
|
|
|
* Ensure that sufficient disks or partitions are available for storage requirements.
|