Exploring compute options in Red Hat OpenShift as a VMware admin
Monitoring, migration, resource balancing, there are several compute options that go into any tool for managing your infrastructure. In this section, we will explore common features in Red Hat® OpenShift®, and what Red Hat® OpenShift® Virtualization compute menu options mean for VMware vSphere admins.
What will you learn?
- How OpenShift menu and features map to ones you may know from VMware
What do you need before starting?
- VMware vSphere 8.0 or higher (as referenced in this path)
- Red Hat OpenShift (as referenced in this path)
Compute feature mapping chart
This section addresses commonly used compute features in VMware and how they map to deploying, managing, and maintaining virtual machines in OpenShift.
and memory
Catalog to manage boot sources, VM templates and instance types.
VMs can be created from VM templates, instance types or declarative raw VM definitions when associated with a specific boot source.
Menu mapping chart
This section addresses what compute menu selection items in OpenShift Virtualization mean from a VMware vSphere perspective. As noted in previous resources, OpenShift is conceptually different in select areas from VMware to achieve the same or similar items. These instances will be marked as "N/A".
NodeHealthChecks
(Node Health Check Operator is needed)
Config > vSphere DRS Configure remediation actions for different node states. There is a range of remediation operators that go from soft rebooting a node that is in Not Ready or Unknown state, hard rebooting it from the BMC APIs or forcing a reinstallation of the node after unsuccessful reboot remediations(Automation) Aria Automation or PowerCLI List and troubleshoot the metadata of nodes installed and automated through the OpenShift Machine API operator using manual or automatic scaling
(Automation)
Host Profiles
Aria Automation + Operators or PowerCLI
List and troubleshoot the metadata of nodes installed and automated through the OpenShift Machine API operator using manual or automatic scaling(Automation) Host Profiles Configure automation profiles to manually or automatically scale infrastructure. A scaled MachineSet will create a Machine object to allocate an available bare metal host and trigger the installation and configuration defined in the MachineSet
(Automation) Aria Automation + Operators or PowerCLI Define autoscaling rules to scale a MachineSet
Bare Metal Host
(Automation)
(additional Operator needed)
Aria Automation + Operators or PowerCLI List and operate bare metal servers added to the cluster. Bare metal hosts include manually installed servers and servers made available for and installed by MachineSet scaling. Integrated with BMC APIs it enables full server lifecycle(Automation)
Host Profiles
Aria Automation + Operators or PowerCLI
Manage declarative host configurations to ensure consistent groups of configurations per machine pools and avoid configuration drifts(Automation)
Host Profiles
Aria Automation + Operators or PowerCLI
Manage different host configuration pools allocating MachineConfig objects to nodes based on roles. MachineConfigPools also allow to segment nodes and define different HA policies when rolling platform updates/upgradesNow that you have explored the common compute options available in OpenShift as to how they pertain to VMware vSphere, it's time to see comparisons between observability offerings.