IBM logoEnterprise Cloud Management SupportContact Us
ArticlesArticles Most Popular ArticlesMost Popular Articles Most Helpful ArticlesMost Helpful Articles Submit A QuestionSubmit A Question
RSS Feeds
DrillDown Icon Table of Contents Back
 . . . . . . . . . . . . .
DrillDown Icon Enterprise Cloud
DrillDown Icon Release Notes
DrillDown Icon Known Issues
DrillDown Icon Policies
DrillDown Icon Registration and Login
DrillDown Icon Infinicenter Console
DrillDown Icon Environments
DrillDown Icon Compute Pools
DrillDown Icon Rename a Compute Pool
DrillDown Icon Add Compute Pools
DrillDown Icon Delete Compute Pools
DrillDown Icon Migrate Virtual Machines; Unassisted
DrillDown Icon Migrate Virtual Machines; Assisted
DrillDown Icon Resources Tab
DrillDown Icon Devices Tab
DrillDown Icon Network Tab
DrillDown Icon Cloud Services Tab
DrillDown Icon Resource Alerts
DrillDown Icon My Account
DrillDown Icon Enterprise Cloud API
DrillDown Icon Best Practices
DrillDown Icon FAQs
DrillDown Icon Troubleshooting
DrillDown Icon Enterprise Cloud Managed Edition
DrillDown Icon Sales and Support
DrillDown Icon Proprietary Statement
  Email This ArticlePrint PreviewPrint Current Article and All Sub-Articles
 
Migrate Virtual Machines Between Compute Pools; Unassisted

Migrate Virtual Machines Between Compute Pools; Unassisted

Organizations can migrate virtual machines between compute pools without assistance from Global Support Services. Organizations that desire assistance from Global Support Services in migrating the settings, see Migrate Virtual Machines; Assisted.

The anticipated use case for migrating virtual machines between compute pools is for organizations that wish to change an existing reserved compute pool into an instance-based compute pool. This article exemplifies this use case. However, this procedure does not preclude migrations between two reserved compute pools, between two instance-based compute pools, or from an instance-based compute pool to a reserved compute pool.

This procedure imposes two limitations:

  • The two compute pools must be in the same environment.
  • Potential billing adjustments can occur in the month in which the migration occurs or the following month.

Prerequisites

The organization must create and sign a contract with sales or client services for an instance-based compute pool and establish the discount tier for billing.

Enterprise Cloud must create a new, instance-based compute pool in the same environment as the existing reserved compute pool.

Copy the Virtual Machines

The virtual machines can be copied in two ways.

Copy Between Compute Pools

The organization can choose to copy the virtual machines between compute pools. The copy identical creates the copied virtual machine configured with the IP address of the source virtual machine, which causes address conflicts on the network if both source and copied virtual machines are powered on. However, the IP address is not assigned to the copied virtual machine in the Enterprise Cloud configuration database or Infinicenter Console; this is a deliberate design feature. Once the organization copies identical virtual machines, the organization must migrate the services and settings between the two virtual machines.

Copy the Virtual Machines to the Destination Compute Pool

Navigate to the source reserved compute pool in Infinicenter Console.

For each virtual machine in the source reserved compute pool:

  1. Shut down the source virtual machine.
  2. Rename the source virtual machine in Infinicenter Console to free the virtual machine names for the new compute pool and to enable rollback, if needed.
  3. Copy each virtual machine in the source reserved compute pool identically to the destination compute pool.
  4. Note: If snapshots are enabled on a virtual machine, the copy identical creates the new virtual machine from the current state of the virtual machine. Snapshots are not copied.

  5. Record the new name of the source virtual machine.
  6. Note: Retain the source virtual machine in the source reserved compute pool to enable rollback, if needed.

Create Inventory

Create an inventory of the virtual machines to migrate. The inventory must include:

  • Name of the source reserved compute pool.
  • Name of source virtual machines.
  • Name of destination instance-based compute pool.
  • Name of destination virtual machines.

Continue with Migrate Services and Settings.

Move Through VM Catalog

The organization can choose to move the source virtual machines through the VM Catalog. This method is always available to the organization.

Copy the Virtual Machines to VM Catalog

Navigate to the source reserved compute pool in Infinicenter Console.

For each virtual machine in the source reserved compute pool:

  1. Shut down the source virtual machine.
  2. Copy each virtual machine in the source reserved compute pool to the VM Catalog.
  3. Note: If snapshots are enabled on a virtual machine, the copy identical creates the new virtual machine from the current state of the virtual machine. Snapshots are not copied.

  4. Rename the source virtual machine in Infinicenter Console to free the virtual machine name for the create procedure.
  5. Note: Retain the source virtual machine in the source reserved compute pool and enable rollback, if needed.

  6. Record the new name of the source virtual machine.
  7. Record the row and group of the source virtual machine.

Create the Virtual Machines from VM Catalog

Navigate to the destination instance-based compute pool in Infinicenter Console.

For each catalog item created from the source reserved compute pool:

  1. Create each destination virtual machine from the VM Catalog in the row and group of the source virtual machine.
  2. Console connect to the new virtual machine and ensure that the proper network and IP settings are configured in new virtual machine.
  3. Record the name of the new virtual machine.

Create Inventory

Create an inventory of the virtual machines to migrate. The inventory must include:

  • Name of the source reserved compute pool.
  • Name of source virtual machines.
  • Name of destination instance-based compute pool.
  • Name of destination virtual machines.

Continue with Migrate Services and Settings.

Migrate Services and Settings

You must have the inventory of virtual machines to migrate, which you created when you copied the virtual machines.

Remove Services Associated with Source Virtual Machines

In the source compute pool, remove services in which the source virtual machines participate.

    Remove Firewall Logging

  1. Go to Environments > Network > Security Services.
  2. Click Firewall Log.
  3. The Firewall Log Server Location dialog appears.

  4. Check if the firewall log is sent to any IP address on the inventory.
  5. If the firewall log is sent to an IP address on the inventory, record the IP address to configure.
  6. If the firewall log is sent to an IP address on the inventory, select None and then click Save to stop sending the firewall log to that virtual machine or configure a different IP address.
  7. Remove Device RNATs

  8. Go to Environments > Network > Internet Services.
  9. Click Configure RNATs.
  10. Click Device RNATs.
  11. Search the list of device RNATs for the any IP address of any source virtual machine.
  12. For each device RNAT found for an IP address on the inventory, record the source virtual machine IP address and associated public IP address so you can create the device RNAT for the destination virtual machine.
  13. For each device RNAT found for an IP address on the inventory, remove the device RNAT for the source virtual machine.
  14. Remove Custom Firewall Rules

  15. Go to Environments > Network > Security Services.
  16. Click Export to download a copy of all firewall rules to a spreadsheet.
  17. Search the list of firewall rules for custom firewall rules where the source or destination is a device IP address and the device IP address is an IP address on any source virtual machine.
  18. For each such firewall rule found, record the firewall rule so you can create the firewall rule for the destination virtual machine.
  19. For each such firewall rule found, delete the firewall rule for the source virtual machine.
  20. Remove Node Services

  21. Go to Environments > Network > Internet Services.
  22. Click each public IP address and click Print to print the node services for that public IP address.
  23. Search the node services for any IP address on any source virtual machine.
  24. For each node service found, record the node name, device (virtual machine) name, IP address, protocol, and port of each node service so you can create the node service for the destination virtual machine.
  25. For each node service found, remove the node service for the source virtual machine.

Remove Settings on Source Virtual Machines

For each source virtual machine on the inventory, remove the virtual machine settings.

  1. Go to Environments > Devices.
  2. Click the desired virtual machine.
  3. Remove Snapshots

    Note: If snapshots are enabled on a virtual machine, the copy identical or copy to VM Catalog creates the new virtual machine from the current state of the virtual machine. Snapshots are not copied.

  4. Click Administrative Tasks.
  5. Click Snapshots.
  6. If Enabled is selected, record the configuration to enable snapshots on the destination virtual machine; if Enabled is not selected, snapshots are not configured.
  7. Remove Cloud Services

  8. Click Cloud Services.
  9. For each cloud service:

  10. Click the cloud service.
  11. Click Edit Configuration, if available, and record the configuration to add cloud services on the destination virtual machine; if Edit Configuration is not available, cloud services are not configured.
  12. Click Cloud Services.
  13. Click the cloud service again.
  14. Click Remove Configuration, if available; if Remove Configuration is not available, cloud services are not configured.
  15. Remove IP Addresses

  16. Click Administrative Tasks.
  17. Click Manage IPs.
  18. Select all the assigned IP addresses on the source virtual machine and remove the IP addresses on the source virtual machine.

id="AddSettings"Add Settings on Destination Virtual Machines

For each destination virtual machine on the inventory, add the virtual machine settings.

  1. Go to Environments > Devices.
  2. Click the desired virtual machine.
  3. Add IP Addresses

  4. Add the IP addresses from the inventory to the destination virtual machine.
  5. Add Cloud Services

  6. If cloud services were configured on the source virtual machine, add the cloud services as described under Cloud Services to the destination virtual machine using the configuration recorded earlier.
  7. Add Snapshots

    Note: If snapshots are enabled on a virtual machine, the copy identical or copy to VM Catalog creates the new virtual machine from the current state of the virtual machine. Snapshots are not copied.

  8. If snapshots were enabled on the source virtual machine, enable snapshots on the destination virtual machine using the configuration recorded earlier.

Add Services Associated with Destination Virtual Machines

For the destination compute pool, add services on the destination virtual machines.

    Add Node Services

  1. For each node service recorded earlier, create the node service for the destination virtual machine using the configuration recorded earlier.
  2. Add Custom Firewall Rules

  3. For each custom firewall rule recorded earlier, add the allow or deny firewall rule for the destination virtual machine using the configuration recorded earlier.
  4. Add Device RNATs

  5. For each device RNAT recorded earlier, add the device RNAT for the destination virtual machine using the configuration recorded earlier.
  6. Add Firewall Logging

  7. If the firewall log was sent to an IP address on the inventory, configure a server to receive the firewall log using the IP address recorded earlier.

Test Destination Virtual Machines

  1. Test each destination virtual machine.
  2. Test the services associated with each destination virtual machine.

Delete Source Virtual Machines and Catalog Items

  1. Delete the source virtual machines renamed in step 2 of Copy the Virtual Machines to the Destination Compute Pool or step 2 of Copy the Virtual Machines to VM Catalog earlier.
  2. Note: Failure to remove the source virtual machines (or, alternatively, change the IP addresses) will result in duplicate IP address errors.

  3. Delete the catalog items created in step 1 of Copy the Virtual Machines to VM Catalog earlier, if desired.