Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-3706

Use Existing OVA Image for OpenShift 4.x Installation on VMware vSphere

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Undefined Undefined
    • openshift-4.14
    • openshift-4.9, openshift-4.10, openshift-4.11, openshift-4.12
    • Installer
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      Use Existing OVA Image for OpenShift 4.x Installation on VMware vSphere

      2. What is the nature and description of the request?

      This is a follow-up to the existing RFE-1722.

      Currently, during an IPI installation on vSphere, the installer uploads an OVA image from a bastion host to every vSphere cluster every time the installation is started. This process is time-consuming and inefficient, especially when multiple clusters need to be installed, and especially with disconnected environments.

      I understand that there was a previous request for this enhancement (RFE-1722) which was rejected. However, I would like to bring attention to the difficulties that can be experienced due to this limitation.

      In a disconnected environment, a workaround for this limitation involves using multiple jump point servers to pass the download of the OVA image to the bastion host. However, this approach is not without its challenges. This bastion host and jump servers are not  always replicated on all sites, which means that in the event of a disaster recovery at one site, we would need to urgently deploy another bastion and multiple jump point servers on a different site. This can add unnecessary steps and delay the time it takes to recreate the clusters, as well as introduce additional network and firewall issues.

      We would like to request the ability to point the installer to an existing OVA image that is already stored in VMware vSphere. This enhancement would greatly minimize the time it takes to recreate clusters and reduce the risk of clusters not being able to reinstall during a DR event.

      3. Why does the customer need this? (List the business requirements here)

      • Remote work uploading a new template via VPN and/or jump servers is a hassle
      • with multiple cluster having the same template multiple times is a waste.
      • save time during installation testing and DR
      • easier management of templates at a central place for vSphere management
      • minimize the time it takes to recreate clusters
      • reduce the risk of clusters not being able to reinstall during a DR event

      4. List any affected packages or components.

      OpenShift 4.x vSphere installer

              racedoro@redhat.com Ramon Acedo
              rh-ee-dcoronel David Coronel
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: