Migrating from IBM Cloud Orchestrator V2.4.0.2 or later
You can migrate a non high-availability IBM® Cloud Orchestrator environment with VMware, KVM, or PowerVC regions which use Neutron networks from IBM Cloud Orchestrator V2.4 Fix Pack 2 or later fix pack to IBM Cloud Orchestrator V2.5.0.2 which uses IBM Cloud Manager with OpenStack as OpenStack distribution.
If you want to migrate from a version older than 2.4.0.2, you must first upgrade to IBM Cloud Orchestrator V2.4.0.2. For more information about upgrading to IBM Cloud Orchestrator V2.4.0.2, see Upgrading. If you want to upgrade from IBM Cloud Orchestrator V2.5, V2.5.0.1, or V2.5.0.1 interim fix 1, see Upgrading from IBM Cloud Orchestrator V2.5.
The following IBM Cloud
Orchestrator V2.4.0.2
configurations or resources are not supported for migration
to IBM Cloud
Orchestrator V2.5.0.2:
- IBM Cloud Orchestrator systems in high-availability configuration.
- Regions that use z/VM® or HyperV hypervisors.
- Regions that use Nova networks.
- Virtual system patterns that are defined by using Workload Deployer. Existing deployed patterns are migrated as individual instances. In IBM Cloud Orchestrator V2.5.0.2, you can use OpenStack Heat templates.
- Any customization that was done to the OpenStack configuration files in the IBM Cloud
Orchestrator V2.4.0.2
environment to support a specific configuration (for example, the VMware advanced configuration). You must manually reapply your
customization after you deploy the IBM Cloud Manager with OpenStack
controllers.Important: Before you reapply your OpenStack customization, see the hypervisor details in Prerequisites for IBM Cloud Manager with OpenStack section.