openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

CNV-50248: Added a section with vSphere functionality mapping

Browse Source
This commit is contained in:
Jaromir Hradilek
2024-11-27 15:05:02 +01:00
parent 90a67098db
commit df2a033428
3 changed files with 57 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
modules/virt-supported-cluster-version.adoc
View File

@@ -1,8 +1,9 @@
// Module included in the following assemblies:
//
// * virt/about_virt/about-virt.adoc
// * virt/virt_release_notes/virt-4-9-release-notes.adoc
[id="virt-supported-cluster-version_{context}"]
= {VirtProductName} supported cluster version
= Supported cluster versions for {VirtProductName}
{VirtProductName} {VirtVersion} is supported for use on {product-title} {product-version} clusters. To use the latest z-stream release of {VirtProductName}, you must first upgrade to the latest version of {product-title}.
{VirtProductName} {VirtVersion} is supported for use on {product-title} {product-version} clusters. To use the latest z-stream release of {VirtProductName}, you must first upgrade to the latest version of {product-title}.

51
modules/virt-vmware-comparison.adoc Normal file
View File

@@ -0,0 +1,51 @@
// Module included in the following assemblies:
//
// * virt/about_virt/about-virt.adoc
:_mod-docs-content-type: REFERENCE
[id="virt-vmware-comparison_{context}"]
= Comparing {VirtProductName} to {vmw-full}
If you are familiar with {vmw-first}, the following table lists {VirtProductName} components that you can use to accomplish similar tasks. However, because {VirtProductName} is conceptually different from {vmw-short}, and much of its functionality comes from the underlying {product-title}, {VirtProductName} does not have direct alternatives for all {vmw-short} concepts or components.
.Mapping of {vmw-short} concepts to their closest {VirtProductName} counterparts
[options="header"]
[cols="2,2,3"]
|===
|{vmw-short} concept |{VirtProductName} |Explanation
|Datastore
|Persistent volume (PV){nbsp}+ +
Persistent volume claim (PVC)
|Stores VM disks. A PV represents existing storage and is attached to a VM through a PVC. When created with the `ReadWriteMany` (RWX) access mode, PVCs can be mounted by multiple VMs simultaneously.
|Dynamic Resource Scheduling (DRS)
|Pod eviction policy{nbsp}+ +
Descheduler
|Provides active resource balancing. A combination of pod eviction policies and a descheduler allows VMs to be live migrated to more appropriate nodes to keep node resource utilization manageable.
|NSX
|Multus{nbsp}+ +
OVN-Kubernetes{nbsp}+ +
Third-party container network interface (CNI) plug-ins
|Provides an overlay network configuration. There is no direct equivalent for NSX in {VirtProductName}, but you can use the OVN-Kubernetes network provider or install certified third-party CNI plug-ins.
|Storage Policy Based Management (SPBM)
|Storage class
|Provides policy-based storage selection. Storage classes represent various storage types and describe storage capabilities, such as quality of service, backup policy, reclaim policy, and whether volume expansion is allowed. A PVC can request a specific storage class to satisfy application requirements.
|vCenter +
vRealize Operations
|OpenShift Metrics and Monitoring
|Provides host and VM metrics. You can view metrics and monitor the overall health of the cluster and VMs by using the {product-title} web console.
|vMotion
|Live migration
|Moves a running VM to another node without interruption. For live migration to be available, the PVC attached to the VM must have the `ReadWriteMany` (RWX) access mode.
|vSwitch +
DvSwitch
|NMState Operator{nbsp}+ +
Multus
|Provides a physical network configuration. You can use the NMState Operator to apply state-driven network configuration and manage various network interface types, including Linux bridges and network bonds. With Multus, you can attach multiple network interfaces and connect VMs to external networks.
|===

4
virt/about_virt/about-virt.adoc
View File

@@ -43,7 +43,9 @@ ifdef::openshift-rosa,openshift-dedicated[]
You can check your {VirtProductName} cluster for compliance issues by installing the Compliance Operator and running a scan with the `ocp4-moderate` and `ocp4-moderate-node` profiles. The Compliance Operator uses OpenSCAP, a link:https://www.nist.gov/[NIST-certified tool], to scan and enforce security policies.
endif::openshift-rosa,openshift-dedicated[]
include::modules/virt-supported-cluster-version.adoc[leveloffset=+2]
include::modules/virt-vmware-comparison.adoc[leveloffset=+1]
include::modules/virt-supported-cluster-version.adoc[leveloffset=+1]
include::modules/virt-about-storage-volumes-for-vm-disks.adoc[leveloffset=+1]