Este contenido no está disponible en el idioma seleccionado.
Chapter 1. Provisioning devices
- You can provision devices with the Red Hat Edge Manager in different environments. Use the operating system image or disk image that you built for use with the Red Hat Edge Manager and depending on your target environment, provision a physical or virtual device.
Required access: Cluster administrator
See the following documentation:
1.1. Provisioning physical devices Copiar enlaceEnlace copiado en el portapapeles!
-
When you build an ISO disk image from an operating system image by using the
bootc-image-buildertool, the image is similar to the RHEL ISOs available for download. However, your operating system image content is embedded in the ISO disk image.
To install the ISO disk image to a bare metal system without having access to the network, see Deploying a custom ISO container image.
For information about installing the ISO through the network, see Deploying an ISO bootc image over PXE boot.
1.2. Provisioning devices on OpenShift Virtualization Copiar enlaceEnlace copiado en el portapapeles!
- You can provision a virtual machine on OpenShift Virtualization by using a QCoW2 container disk image that is hosted on an OCI container registry.
If your operating system image does not already contain the Red Hat Edge Manager agent enrollment configuration, you can inject the configuration through the cloud-init user data at provisioning.
For more information, see the Additional resources section.
1.2.1. Prerequisites Copiar enlaceEnlace copiado en el portapapeles!
-
You installed the
flightctlCLI and logged in to your Red Hat Edge Manager service instance. -
You installed the
ocCLI, used it to log in to your OpenShift cluster instance, and changed to the project in which you want to create your virtual machine.
1.2.2. Creating the cloud-init configuration Copiar enlaceEnlace copiado en el portapapeles!
To create the cloud-init configuration, complete the following steps:
Request a new Red Hat Edge Manager agent enrollment configuration and store it in a file called
config.yaml. Run the following command:flightctl certificate request --signer=enrollment --expiration=365d --output=embedded > config.yaml
flightctl certificate request --signer=enrollment --expiration=365d --output=embedded > config.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create a cloud configuration user data file called
cloud-config.yamlthat places the agent configuration in the correct location on the first boot. Run the following command:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create a Kubernetes
Secretthat contains the cloud configuration user data file:oc create secret generic enrollment-secret --from-file=userdata=cloud-config.yaml
oc create secret generic enrollment-secret --from-file=userdata=cloud-config.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow
1.2.3. Creating the virtual machine Copiar enlaceEnlace copiado en el portapapeles!
Create a virtual machine that has its primary disk populated from your QCoW2 container disk image and a cloud-init configuration drive that is populated from your enrollment secret. Complete the following steps:
Create a file that contains a the
VirtualMachineresource manifest by running the following command:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Apply the resource manifest to your cluster by running the following command:
oc apply -f my-bootc-vm.yaml
oc apply -f my-bootc-vm.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow
1.2.4. Additional resources Copiar enlaceEnlace copiado en el portapapeles!
-
For more information about how to inject the configuration through the
cloud-inituser data, see Cloud-init documentation. - See Building for specific target platforms.