You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Much improved deployment to Libvirt, see the openshift_libvirt_fwcfg.yml playbook.
Creating virtual machines using a shared template disk image.
Ignition configuration is passed via QEMU firmware config which avoids the need for PXE booting.
The Libvirt installation using PXE boot is still available as a separate playbook openshift_libvirt_pxe.yml as it's useful for testing the PXE boot provisioning, and in contrast to the QEMU firmware config method, PXE boot works for the older RHEL7-based hypervisors.
vSphere deployment doesn't require HTTP server anymore. HTTP server was used to serve ignition files to OpenShift nodes. Ignition files are now sent to the vSphere APIs in their entirety and attached to OpenShift VMs as custom attributes. vSphere APIs don't specify the maxium allowed size for custom attributes, see also the respective WSDL definition I was able to upload up to 12 MB of data as custom attributes. The size of a typical ignition config file is less than 0.5 MB.
openshift-auto-upi is now going to power up only newly created virtual machines. Existing virtual machines which are part of the cluster are left intact.
