红帽全球峰会此内容没有您所选择的语言版本。
Chapter 13. Provisioning virtual machines on OpenShift Virtualization
OpenShift Virtualization addresses the needs of development teams that have adopted or want to adopt Red Hat OpenShift Container Platform but possess existing virtual machine (VM) workloads that cannot be easily containerized. This technology provides a unified development platform where developers can build, modify, and deploy applications residing in application containers and VMs in a shared environment. These capabilities support rapid application modernization across the open hybrid cloud.
You can create a compute resource for OpenShift Virtualization so that you can provision and manage virtual machines in OpenShift Container Platform by using Satellite.
Note that template provisioning is not supported for this release.
The OpenShift Virtualization compute resource is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
Prerequisites
- You can use synchronized content repositories for Red Hat Enterprise Linux. For more information, see Synchronizing repositories in Managing content.
- Provide an activation key for host registration. For more information, see Creating an activation key in Managing content.
-
You must have
cluster-adminpermissions for the OpenShift Container Platform cluster. - A Capsule Server managing a network on the OpenShift Container Platform cluster. Ensure that no other DHCP services run on this network to avoid conflicts with Capsule Server. For more information about network service configuration for Capsule Servers, see Preparing networking in Provisioning hosts.
- Ensure the provisioning user has the required permissions to provision hosts. For more information, see Appendix D, Permissions required to provision hosts.
By default, deleting a host entry associated with a virtual machine does not destroy the virtual machine on the compute resource.
To change the default behavior, navigate to Administer > Settings > Provisioning and set Destroy associated VM on host delete to Yes.
Use this procedure to add OpenShift Virtualization as a compute resource in Satellite.
Procedure
Enter the following
satellite-installercommand to enable the OpenShift Virtualization plugin for Satellite:satellite-installer --enable-foreman-plugin-kubevirt
# satellite-installer --enable-foreman-plugin-kubevirtCopy to Clipboard Copied! Toggle word wrap Toggle overflow Obtain a token to use for HTTP and HTTPs authentication:
Log in to the OpenShift Container Platform cluster and list the secrets that contain tokens:
oc get secrets
$ oc get secretsCopy to Clipboard Copied! Toggle word wrap Toggle overflow Obtain the token for your secret:
oc get secrets MY_SECRET -o jsonpath='{.data.token}' | base64 -d | xargs$ oc get secrets MY_SECRET -o jsonpath='{.data.token}' | base64 -d | xargsCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Record the token to use later in this procedure.
- In the Satellite web UI, navigate to Infrastructure > Compute Resources, and click Create Compute Resource.
- In the Name field, enter a name for the new compute resource.
- From the Provider list, select OpenShift Virtualization.
- In the Description field, enter a description for the compute resource.
- In the Hostname field, enter the FQDN, hostname, or IP address of the OpenShift Container Platform cluster.
- In the API Port field, enter the port number that you want to use for provisioning requests from Satellite to OpenShift Virtualization.
- In the Namespace field, enter the user name of the OpenShift Container Platform cluster.
- In the Token field, enter the bearer token for HTTP and HTTPs authentication.
- Optional: In the X509 Certification Authorities field, enter a certificate to enable client certificate authentication for API server calls.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}