The document outlines the steps to migrate an IBM Cloud Orchestrator environment from version 2.4.0.2 to 2.5.0.1. The key steps include: 1) checking prerequisites and discovering the topology, 2) migrating images between the systems, 3) exporting OpenStack data from the original system, 4) importing the data into the new IBM Cloud Manager, and 5) verifying the migrated resources on both systems and ensuring resources are no longer available on the original system.

1. Migrating IBM Cloud
Orchestrator environment from
v2.4.0.2 to v2.5.0.1
By Paulraj Pappaiah

2. Migrating IBM Cloud Orchestrator environment from v2.4.0.2 to v2.5.0.1
Objective:
The following sample steps explains you to migrating from IBM Cloud Orchestrator v2.4.0.2 to v2.5.0.1.
For more clarity, go to IBM Knowledge Center refer the latest materials.
Migration Steps:
• Check Pre-Requisite
• Migrate Images ( Glance)
• Export OpenStack Data
• Import IBM Cloud Manager with OpenStack Controller
• Verify the resources on IBM Cloud Orchestrator
• Verify the resources on IBM Cloud Manager and OpenStack
• Verify migration details
Caution: Purpose of this presentation teach you the step by step approach for just for an understanding and not responsible for any professional or community related approaches, installations, configuration, setup etc.,

3. Migrating IBM Cloud Orchestrator environment from v2.4.0.2 to v2.5.0.1
Step-1 (Pre Requisite)
• Logon as "Root" user
• On the IBM Cloud Orchestrator v2.5.0.1 server
• Edit ico_upgrade.rsp response file.
• Check pre-requisite packages
• Execute ./upgrade-prereq-checker.py ico_upgrade.rsp shell script
• Wait for the script to finish the execution
• Verify the checks, success/failure, warning etc.,
• If you notify any failure on the pre-requisite checker then verify and edit the upgrade response file
and fix the errors and re-run the file.
• Discover the topology by the following command
• Execute ./upgrade.py ico_upgrade.rsp --discover
• Wait for the script to finish the execution
• Verify the checks, success/failure, warning etc.,
• Check the details; If you notify any failure on the pre-requisite checker then edit and verify upgrade
file thoroughly and fix the errors and re-run the file.
• The discovery reports are created in the /tmp/discovery directory
• Go to cd /tmp/discovery/
• Enter ls -latr
• Use Cat command to view "discovered25Regions.json" file
• Check the migrated regions, un-migrated regions, unattached pre-pared regions
• Check "discoveryMigrationReport.html" file in a browse to ensure details

4. Migrating IBM Cloud Orchestrator environment from v2.4.0.2 to v2.5.0.1
• Step-2 ( Migrate Images )
• Migrate all the images are belongs in Glance on the IBM Cloud Orchestrator v2.4.0.2 Region Server to
the IBM Cloud Manager with OpenStack Controller
• Executive " ./upgrade-prereq-checker.py ico.upgrade.rsp --check-regions
• Wait for the script to finish the execution
• Verify the checks, success/failure, warning etc.,
• If you notify any failure on the pre-requisite checker then verify and edit the upgrade response file
thoroughly and fix the errors and re-run the file.
• Migrate all the images are belongs in Glance on the IBM Cloud Orchestrator v2.4.0.2 Region Server to
the IBM Cloud Manager with OpenStack Controller
• Execute the command
• ./upgrade.py ico_upgrade.rsp .-copy-images
• Wait for the script to finish the execution
• Check the details; If you notify any failure on the migration script then edit and verify the upgrade
response file thoroughly and fix the errors and re-run the file

5. Migrating IBM Cloud Orchestrator environment from v2.4.0.2 to v2.5.0.1
• Step-3 ( Export OpenStack data)
• Export OpenStack data from IBM Cloud Orchestrator v2.4.0.2 Region Server to imports the
data in the IBM Cloud Manager with OpenStack Controller.
• Note: The export script will stop Region Server services and disable and no longer manager the
hypervisor
• Execute the export script
• ./upgrade.py ico_upgrade.rsp --export-region
• Wait for the script to finish the execution
• Check the details; If you notify any failure on the export script then edit and verify the upgrade
response file thoroughly and fix the errors and re-run the file

6. Migrating IBM Cloud Orchestrator environment from v2.4.0.2 to v2.5.0.1
Step-4 ( Import IBM Cloud Manager with OpenStack Controller )
• Import from the previous steps in the IBM Cloud Manager with OpenStack controller
• Execute the import script
• ./upgrade.py ico_upgrade.rsp --import-region
• If you notify any failure on the import script then edit and verify the upgrade response file
thoroughly and fix the errors and re-run the file
• Wait for the script to finish the execution
• Check the details; If you notify any failure on the import script then edit and verify the upgrade
response file thoroughly and fix the errors and re-run the file

7. Migrating IBM Cloud Orchestrator environment from v2.4.0.2 to v2.5.0.1
Step-5 ( Verify the resources on ICO)
• Open IBM Cloud Orchestrator v2.5.0.1
• Logon as "admin" user
• Go to "Resource" page
• Check migrated resources

8. Migrating IBM Cloud Orchestrator environment from v2.4.0.2 to v2.5.0.1
Step-6 ( Verify the resources on ICMO )
• Open IBM Cloud Manager
• Logon as "admin" user
• Open Networks from the Dashboard
• Check migrated resources
• Click on the resources and see Network Overview
• Identify the user details

9. Migrating IBM Cloud Orchestrator environment from v2.4.0.2 to v2.5.0.1
Step-7 ( Ensure that resources are migrated from v2.4.0.1)
• Open IBM Cloud Orchestrator v2.4.0.1)
• Logon as "admin" user
• If you get an error message, such as " Unable to retrieve hypervisor information" then assume that
the migration effort was successful and no longer resources are available here

10. Thank You