Effectively managing and maintaining the ability to migrate workloads seamlessly is a large part of sustaining a hybrid cloud infrastructure. In this demonstration, we are going to deploy VMware HCX in our on-premises vSphere environment and set up a site-pairing between our on-premises environment and our IBM Cloud SDDC.
Once we have HCX configured, we will test our connectivity by migrating workloads between our sites. We will also configure an extended network between both sites using HCX. This allows virtual machines to move between sites without the need to change IP addresses.
- Click Network Extension in the left column.
- Click Create a Network Extension.
- Select the Source Network you want to extend, in this case, stretch-01.
- Click Next.
- Click into the Gateway IP Address field.
- Type "192.168.8.1/24"
- Click on Mobility Optimized Networking.
- Click Submit.
Notice the status has changed to Extension Complete, migration and creation of workloads on IBM Cloud within the stretch-01 VLAN is now possible.
The Gateway IP Address is the network gateway of the network you chose to extend.
Now that the L2 extension has been completed workloads can be migrated to IBM Cloud on that L2 Extended network and other non-extended networks from your on-premises environment.
1. Click Migration in the left column.
- Click Migrate button at the top of the screen.
- Select from the list App-Production virtual machine.
- Select from the list SQL-Production virtual machine.
- Select from the list Web-Production virtual machine.
- Click the Add button on the top right of the screen.
This adds all the virtual machines you have selected to a migration group. Now, we will be configuring the specific migration details for the group of machines.
- Click the Compute Container drop-down.
- Select Workload-Cluster.
This is the IBM Cloud cluster where these virtual machines will be migrated to.
- Click Select.
- Click the Destination Folder dropdown.
- Select VMs Migrated to cloud.
This is the IBM Cloud folder location where the virtual machines will be put into.
- Click Select.
- Click the Storage dropdown.
- Select vSan Datastore.
This is the IBM Cloud datastore where these virtual machines will be migrated to.
- Click Select.
- Click the Same format as source dropdown.
- Select Thin Provision.
This selection tells VMware HCX what disk format to use with the migration of the virtual machines when they land in IBM Cloud.
- Click the Migration Profile dropdown.
- Select vMotion.
- Select Switchover Schedule.
This selection tells VMware HCX to vMotion all the virtual machines in this migration group to IBM Cloud.
- Click the right arrow (>) next to SQL-Production virtual machine in the list at the bottom of the screen.
Notice that global migration profile details can be changed per virtual machine.
- Scroll down to view further options.
- Click on vMotion dropdown.
- Select Bulk Migration.
The virtual machine migration method for this virtual machine has been changed from vMotion to Bulk Migration.
Bulk migration uses host-based replication to move a virtual machine between HCX data centers.
To reduce the downtime, the source VM remains online during the replication and is bootstrapped on the destination ESX host after replication completes.
- Click on L2E_stretch-01-73730-877dba0e
- Select IBM-Cloud-Dallas.
- Click Select.
Here you have chosen to migrate the virtual machine SQL-Production to the network IBM-Cloud-Dallas network in IBM Cloud. In this example, a new network IP address will be assigned to App-Production on bootup by DHCP in the Dallas IBM Cloud datacenter.
Alternatively, you can customize the network address information for servers with static IP addresses by using the drop-down next to Network Adapter 1
- Click the right arrow (>) next to Network Adapter 1
- Scroll down to view options.
- Click the down arrow next to Network Adapter 1 to condense the information.
- Click the down arrow next to SQL-Production to condense the information.
The migration details of the virtual machine SQL-Production have been changed to Bulk Migration, allowing the IP address to change as part of migration.
After migration to IBM Cloud:
- The SQL-Production virtual machine will be on a new network and have a new IP address.
- The App-Production and Web-Production virtual machine will be running on the stretched L2 network in the Dallas Cloud data center using the same IP address. In this case, a re-IP address of the VM is not required.
The virtual machine migration method for App-Production and Web-Production virtual machine will be vMotion.
Alternatively, the virtual machine migration method for these virtual machines has been changed from vMotion to Replication-assisted vMotion.
- Click Validate.
Prior to migration, a validation step occurs, which checks each virtual machine for its readiness for migration. Notifications can be viewed for each virtual machine, and if needed this is when remediation steps can be taken.
- Click Go.
- Click on migration group in progress. You can expand the VM details using the right arrow next to App-Production, SQL-Production, and Web-Production
Notice the migration progress is now complete.
- Click the browser tab HCX-Dal-Datacenter.vmware.local tab.
- Click App-Production VM. Notice the IP address is still the same on Dallas network on L2E-stretch network.
- Click Web-Production VM. Notice the IP address is still the same on Dallas network on L2E-stretch network.
- Click on Network Icon.
You are now IBM-Cloud-Dallas Network. Notice SQL-Production is now on the IBM-Cloud-Dallas network location with a new IP address.
As we have seen from this demonstration, migrating to IBM Cloud using HCX is seamless and incurs no downtime. These attributes make it ideal as part of the broader toolkit for building hybrid cloud infrastructure.#Featured-area-2-home#Featured-area-2