From 413cdd5f98ae16a53616a6c0f21a064f711fe650 Mon Sep 17 00:00:00 2001 From: Srivaralakshmi Date: Tue, 1 Aug 2023 14:57:36 +0530 Subject: [PATCH] Remove-Virt-files --- .../virt-cluster-resource-requirements.adoc | 90 ---------------- virt/install/preparing-cluster-for-virt.adoc | 100 ------------------ 2 files changed, 190 deletions(-) delete mode 100644 modules/virt-cluster-resource-requirements.adoc delete mode 100644 virt/install/preparing-cluster-for-virt.adoc diff --git a/modules/virt-cluster-resource-requirements.adoc b/modules/virt-cluster-resource-requirements.adoc deleted file mode 100644 index 60cccdfdb63a..000000000000 --- a/modules/virt-cluster-resource-requirements.adoc +++ /dev/null @@ -1,90 +0,0 @@ -// Module included in the following assemblies: -// -// * virt/install/preparing-cluster-for-virt.adoc - -:_content-type: REFERENCE -[id="virt-cluster-resource-requirements_{context}"] -= Physical resource overhead requirements - -{VirtProductName} is an add-on to {product-title} and imposes additional overhead that you must account for when planning a cluster. Each cluster machine must accommodate the following overhead requirements in addition to the {product-title} requirements. Oversubscribing the physical resources in a cluster can affect performance. - -[IMPORTANT] -==== -The numbers noted in this documentation are based on Red Hat's test methodology and setup. These numbers can vary based on your own individual setup and environments. -==== - -[discrete] -[id="memory-overhead_{context}"] -== Memory overhead - -Calculate the memory overhead values for {VirtProductName} by using the equations below. - -.Cluster memory overhead - ----- -Memory overhead per infrastructure node ≈ 150 MiB ----- - ----- -Memory overhead per worker node ≈ 360 MiB ----- - -Additionally, {VirtProductName} environment resources require a total of 2179 MiB of RAM that is spread across all infrastructure nodes. - -.Virtual machine memory overhead - ----- -Memory overhead per virtual machine ≈ (1.002 * requested memory) + 146 MiB \ - + 8 MiB * (number of vCPUs) \ <1> - + 16 MiB * (number of graphics devices) <2> ----- -<1> Number of virtual CPUs requested by the virtual machine -<2> Number of virtual graphics cards requested by the virtual machine - -If your environment includes a Single Root I/O Virtualization (SR-IOV) network device or a Graphics Processing Unit (GPU), allocate 1 GiB additional memory overhead for each device. - -[discrete] -[id="CPU-overhead_{context}"] -== CPU overhead - -Calculate the cluster processor overhead requirements for {VirtProductName} by using the equation below. The CPU overhead per virtual machine depends on your individual setup. - -.Cluster CPU overhead - ----- -CPU overhead for infrastructure nodes ≈ 4 cores ----- - -{VirtProductName} increases the overall utilization of cluster level services such as logging, routing, and monitoring. To account for this workload, ensure that nodes that host infrastructure components have capacity allocated for 4 additional cores (4000 millicores) distributed across those nodes. - ----- -CPU overhead for worker nodes ≈ 2 cores + CPU overhead per virtual machine ----- - -Each worker node that hosts virtual machines must have capacity for 2 additional cores (2000 millicores) for {VirtProductName} management workloads in addition to the CPUs required for virtual machine workloads. - -.Virtual machine CPU overhead - -If dedicated CPUs are requested, there is a 1:1 impact on the cluster CPU overhead requirement. Otherwise, there are no specific rules about how many CPUs a virtual machine requires. - -[discrete] -[id="storage-overhead_{context}"] -== Storage overhead - -Use the guidelines below to estimate storage overhead requirements for your {VirtProductName} environment. - -.Cluster storage overhead - ----- -Aggregated storage overhead per node ≈ 10 GiB ----- - -10 GiB is the estimated on-disk storage impact for each node in the cluster when you install {VirtProductName}. - -.Virtual machine storage overhead - -Storage overhead per virtual machine depends on specific requests for resource allocation within the virtual machine. The request could be for ephemeral storage on the node or storage resources hosted elsewhere in the cluster. {VirtProductName} does not currently allocate any additional ephemeral storage for the running container itself. - -.Example - -As a cluster administrator, if you plan to host 10 virtual machines in the cluster, each with 1 GiB of RAM and 2 vCPUs, the memory impact across the cluster is 11.68 GiB. The estimated on-disk storage impact for each node in the cluster is 10 GiB and the CPU impact for worker nodes that host virtual machine workloads is a minimum of 2 cores. \ No newline at end of file diff --git a/virt/install/preparing-cluster-for-virt.adoc b/virt/install/preparing-cluster-for-virt.adoc deleted file mode 100644 index 0d1b245f5b8b..000000000000 --- a/virt/install/preparing-cluster-for-virt.adoc +++ /dev/null @@ -1,100 +0,0 @@ -:_content-type: ASSEMBLY -include::_attributes/common-attributes.adoc[] -[id="preparing-cluster-for-virt"] -= Preparing your cluster for {VirtProductName} -:context: preparing-cluster-for-virt -:toclevels: 3 - -toc::[] - -Review this section before you install {VirtProductName} to ensure that your cluster meets the requirements. - -[IMPORTANT] -==== -You can use any installation method, including user-provisioned, installer-provisioned, or assisted installer, to deploy {product-title}. However, the installation method and the cluster topology might affect {VirtProductName} functionality, such as snapshots or live migration. -==== - -//// -.FIPS mode - -If you install your cluster in xref:../../installing/installing-fips.adoc#installing-fips-mode_installing-fips[FIPS mode], no additional setup is required for {VirtProductName}. -//// - -.IPv6 - -You cannot run {VirtProductName} on a single-stack IPv6 cluster. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2193267[*BZ#2193267*]) - -include::modules/virt-hardware-os-requirements.adoc[leveloffset=+1] - -* If your cluster uses worker nodes with different CPUs, live migration failures can occur because different CPUs have different capabilities. To avoid such failures, use CPUs with appropriate capacity for each node and set node affinity on your virtual machines to ensure successful migration. See xref:../../nodes/scheduling/nodes-scheduler-node-affinity.adoc#nodes-scheduler-node-affinity-configuring-required_nodes-scheduler-node-affinity[Configuring a required node affinity rule] for more information. - -[role="_additional-resources"] -.Additional resources - -* xref:../../architecture/architecture-rhcos.adoc#rhcos-about_architecture-rhcos[About RHCOS]. -* link:https://catalog.redhat.com[Red Hat Ecosystem Catalog] for supported CPUs. -* xref:../../storage/index.adoc#storage-overview[Supported storage]. - -include::modules/virt-cluster-resource-requirements.adoc[leveloffset=+1] - -include::modules/virt-about-storage-volumes-for-vm-disks.adoc[leveloffset=+1] - -[role="_additional-resources"] -.Additional resources - -* xref:../../storage/index.adoc#openshift-storage-common-terms_storage-overview[Glossary of common terms for {product-title} storage] - -[id="object-maximums_{context}"] -== Object maximums - -You must consider the following tested object maximums when planning your cluster: - -* xref:../../scalability_and_performance/planning-your-environment-according-to-object-maximums.html#planning-your-environment-according-to-object-maximums[{product-title} object maximums]. -* link:https://access.redhat.com/articles/6571671[{VirtProductName} object maximums]. - -[id="restricted-networks-environments_{context}"] -== Restricted network environments - -If you install {VirtProductName} in a restricted environment with no internet connectivity, you must xref:../../operators/admin/olm-restricted-networks.adoc#olm-restricted-networks[configure Operator Lifecycle Manager for restricted networks]. - -If you have limited internet connectivity, you can xref:../../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[configure proxy support in Operator Lifecycle Manager] to access the Red Hat-provided OperatorHub. - -[id="live-migration_{context}"] -== Live migration - -Live migration has the following requirements: - -* Shared storage with `ReadWriteMany` (RWX) access mode. -* Sufficient RAM and network bandwidth. -* If the virtual machine uses a host model CPU, the nodes must support the virtual machine's host model CPU. - -// The HA section actually belongs to OpenShift, not Virt -[id="cluster-high-availability-options_{context}"] -== Cluster high-availability options - -You can configure one of the following high-availability (HA) options for your cluster: - -* Automatic high availability for xref:../../installing/installing_bare_metal_ipi/ipi-install-overview.adoc#ipi-install-overview[installer-provisioned infrastructure] (IPI) is available by deploying xref:../../machine_management/deploying-machine-health-checks.adoc#machine-health-checks-about_deploying-machine-health-checks[machine health checks]. -+ -[NOTE] -==== -In {product-title} clusters installed using installer-provisioned infrastructure and with MachineHealthCheck properly configured, if a node fails the MachineHealthCheck and becomes unavailable to the cluster, it is recycled. What happens next with VMs that ran on the failed node depends on a series of conditions. See xref:../../virt/virtual_machines/virt-create-vms.adoc#virt-about-runstrategies-vms_virt-create-vms[About RunStrategies for virtual machines] for more detailed information about the potential outcomes and how RunStrategies affect those outcomes. -==== - -* Automatic high availability for both IPI and non-IPI is available by using the *Node Health Check Operator* on the {product-title} cluster to deploy the `NodeHealthCheck` controller. The controller identifies unhealthy nodes and uses the Self Node Remediation Operator to remediate the unhealthy nodes. For more information on remediation, fencing, and maintaining nodes, see the link:https://access.redhat.com/documentation/en-us/workload_availability_for_red_hat_openshift/23.2/html-single/remediation_fencing_and_maintenance/index#about-remediation-fencing-maintenance[Workload Availability for Red Hat OpenShift] documentation. - -+ --- -ifdef::openshift-enterprise[] -:FeatureName: Node Health Check Operator -include::snippets/technology-preview.adoc[leveloffset=+2] -:!FeatureName: -endif::[] --- - -* High availability for any platform is available by using either a monitoring system or a qualified human to monitor node availability. When a node is lost, shut it down and run `oc delete node `. -+ -[NOTE] -==== -Without an external monitoring system or a qualified human monitoring node health, virtual machines lose high availability. -====