Red Hat OpenShift Virtualization
You can detect and monitor resources from Red Hat OpenShift Virtualization through a new or existing target configuration with Red Hat OpenShift.
Red Hat OpenShift Virtualization is an included feature of Red Hat OpenShift, and provides a platform for running and deploying new and existing VM workloads. Red Hat OpenShift Virtualization allows for the migration and management of traditional virtual machines onto a trusted, consistent, and comprehensive hybrid cloud application platform.
By configuring a target to discover Red Hat OpenShift Virtualization resources, you can use Turbonomic to monitor and complete actions against these resources to optimize your resource performance.
Configuring the target connection
To discover Red Hat OpenShift Virtualization resources with Turbonomic, you need to configure a target connection with Red Hat OpenShift. Once this target configuration connection is established, Turbonomic can begin to detect both your Red Hat OpenShift and Red Hat OpenShift Virtualization resources.
Prerequisites: In addition to the prerequisites for setting up a Red Hat OpenShift cluster, you need Red Hat OpenShift Virtualization deployed within its own namespace. Ensure that your version of Red Hat OpenShift is version 4.16 or later.
- Extend an existing target connection to Red Hat OpenShift to include a new addition of Red Hat OpenShift Virtualization.
Simply install Red Hat OpenShift Virtualization within Red Hat OpenShift. After the next discovery cycle, Turbonomic begins to detect the new Red Hat OpenShift Virtualization resources.
- Establish a new connection to Red Hat OpenShift with Red Hat OpenShift Virtualization.
Ensure that both Red Hat OpenShift and Red Hat OpenShift Virtualization are installed. Then, create the target configuration to Red Hat OpenShift. As part of creating this target configuration, you must download a script from Turbonomic to run in Red Hat OpenShift. This script creates and deploys the assets that are needed for configuring the target connection with Red Hat OpenShift, and for detecting and setting up the configuration with Red Hat OpenShift Virtualization. Resources from both are detected by Turbonomic through the single target configuration.
For more information and instructions for setting up a target configuration with Red Hat OpenShift, see Connecting to Red Hat OpenShift clusters.
Monitored resources
In addition to the monitored resources for Red Hat OpenShift, resources are monitored specifically for Red Hat OpenShift Virtualization. For details, see Container platform monitored resources.
Viewing resources in Turbonomic
With your Red Hat OpenShift Virtualization resources discovered, you can view the resources within the Turbonomic UI. For instance, on the Application view tab of your Home page, you can see that the supply chain is populated with the resources discovered from Red Hat OpenShift Virtualization and Red Hat OpenShift. The monitored resources, which exist as a virtual machine entity in Red Hat OpenShift, are displayed as workload controllers in Turbonomic, and are of a virtual machine type.
- From the Search page, select Container Pods.
- Then, click the Filter icon to add a filter.
- On the Add filter page, select to Add criteria.
- Configure the following filter:
- Select to add a Tags filter.
- Select Equals.
- For the Tag name, select isVirtualMachineInstance.
- For the Tag value, enter true.
You can also view any associated actions for the resource on the Actions tab of the details view for the resource.
Actions
In addition to the actions that are supported for Red Hat OpenShift, some actions are supported specifically for Red Hat OpenShift Virtualization. For details, see Virtual machine actions.
Policy constraints for Red Hat OpenShift Virtualization VMs
Virtual machines in Red Hat OpenShift Virtualization are represented as workload controllers in Turbonomic. To configure settings and control action behavior for these virtual machines, you need to modify policies at two levels:
-
Container pod policies: To control move actions.
-
Workload controller policies: To control resize actions.
For detailed information about policy constraints and configuration steps, see Virtual machine actions.