--- name: vmwaresolutions-cr_orderinginstance-gen-info title: General information and licensing description: As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026. last-updated: 2025-10-24 --- > ## Documentation Index > The table of contents for this documentation set is at https://cloud.ibm.com/docs/vmwaresolutions?format=markdown > The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt > Use these files to discover more information as needed. # General information and licensing {: #cr_orderinginstance-gen-info} As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026. {: deprecated} The following VMware® components are part of the Cyber Recovery instance. * VMware vSphere® 7.0u3 or 8.0u2 * VMware NSX® 4.1 ## VMware vSphere version {: #cr_orderinginstance-vsphere-license} * vSphere Enterprise Plus 8 is selected by default and is supported only for primary instances. * vSphere 7 is also available to order. ## VMware vCenter Server version {: #cr_orderinginstance-vcenter-license} For existing instances or clusters with vCenter Server 7, you can add only vCenter Server 7 clusters or hosts. CONTENT: The VMware® licensing model is changed. You are entitled to the [VMware software products](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vmwaresol_packaging-pricing&format=markdown#vmwaresol_packaging-pricing-impact) that are included in the VMware Cloud Foundation™ bundle. To request VMware NSX® license upgrades and other licensing changes, open an IBM Support ticket by following the steps in [Getting help and support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support&format=markdown). ## Instance name {: #cr_orderinginstance-inst-name} The instance name is set to **vcs-_xx_** by default, where _xx_ represents two randomly generated alphabetic characters. CONTENT: You can also specify a cluster name that meets the following requirements: * Only lowercase alphabetic, numeric, and hyphen (-) characters are allowed. * The cluster name must start with a lowercase alphabetic character. * The cluster name must end with a lowercase alphabetic or numeric character. * The maximum length of the cluster name is 10 characters. * The cluster name must be unique within your account. ## Resource group {: #cr_orderinginstance-resource-group} If **No resource group available** is displayed in this field, you currently do not have permissions to any resource group in this account. Contact the account owner to be assigned an Editor or Administrator role on a resource group in the account. For more information, see [IBM Cloud IAM roles](https://cloud.ibm.com/docs/iam?topic=iam-userroles&format=markdown). {: note} Click **Browse configurations** to open the configuration manager side pane. Here, you can choose a configuration from the list of saved templates to update it and then save it as a new configuration template. ## Instance configuration name {: #cr_orderinginstance-inst-config} If you do not see any configurations in the list, then you do not have any saved templates and might want to create one. To create a configuration, first specify the settings for your instance as a configuration template without placing an order. To save the settings, click **Save configuration** on the **Summary** pane. Select whether to order a new primary instance or a secondary instance for an existing primary instance. ## Instance type {: #cr_orderinginstance-primary-secondary} CONTENT: * If you are planning to use vSAN™ OSA storage, you can order 4-51 servers. * If you are planning to use vSAN ESA storage, you can order 3-51 servers. * If you are planning to use NFS storage, you can order 3-51 servers. * All servers that you order have the same configuration. ## Licensing (BYOL only) {: #cr_orderinginstance-licensing-settings} Bring Your Own License (BYOL) is no longer supported except for migrations or upgrades of existing BYOL clusters. Add a host to a BYOL cluster only if you are upgrading or migrating an existing BYOL cluster. {: attention} If you are a BYOL user, provide your own license keys for VMware vCenter Server® (Enterprise Plus edition), vSphere (Enterprise Plus edition), and VMware NSX® (Data Center SP Enterprise Plus). Toggle the **BYOL** switch to **Enabled** and enter your license keys. ## Related links {: #cr_orderinginstance-gen-info-related} * [Cyber Recovery overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_overview&format=markdown) * [Planning for Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_planning&format=markdown) * [Requirements for Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_orderinginstance_reqs&format=markdown) * [Procedure to order Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_orderinginstance-order-procedure&format=markdown)