redhat-cloud-suite-migration-demo.adoc

Table of Contents

• Red Hat Cloud Suite Virtualization Migration Demo
• 1. Overview
  • 1.1. Environment
  • 1.2. Provision Your Demo Environment
• 2. Getting Started
  • 2.1. Validate the Current VMs
• 3. Migrate a VM from VMware to Red Hat Enterprise Virtualization
  • 3.1. Configure Red Hat Enterprise Virtualization as a Migration Destination
  • 3.2. Configure VMware as a Migration Source
  • 3.3. Set VM Migration Attributes
  • 3.4. Set VM Migration Tags
  • 3.5. Check Tags and Attributes
  • 3.6. Start VM Migration
  • 3.7. Verify VM Migration
• 4. Migrate a VM From VMware to OpenStack Platform
• 5. Migrate a VM From Red Hat Enterprise Virtualization to OpenStack Platform
• 6. End State
• 7. Extra Credit

Red Hat Cloud Suite Virtualization Migration Demo

1. Overview

This demonstration uses Red Hat CloudForms 3.2 as a broker to drive virtual-to-virtual tools such as ovftool and virt-v2v to migrate VMs from VMware vSphere to Red Hat Enterprise Virtualization and from Red Hat Enterprise Virtualization to Red Hat Enterprise Linux OpenStack Platform 7.

Goal

• Migrate the VMs created in the Red Hat Cloud Suite Deployment demo

Prerequisites

• Completion of the Red Hat Cloud Suite Deployment demo

• The following provisioned VMs:

  • wp1 - a Red Hat Enterprise Linux 7 host running Apache and WordPress

  • wp2 - a Red Hat Enterprise Linux 7 host running Apache and WordPress

  • haproxy - a Red Hat Enterprise Linux 7 host running the HAProxy tool configured to proxy traffic to wp1 and wp2

  • mysql- a Red Hat Enterprise Linux 7 host running MariaDB that the wp1 and wp2 hosts talk to

1.1. Environment

The demo environment consists of the following systems:

Hostname	Internal IP	Description
demo.cloudlab.redhat.com	172.16.0.10	Jump host and iSCSI/NFS server
ipa.cloudlab.redhat.com	172.16.0.15	IPA server managed by Satellite, serves rhcs.cloudlab.redhat.com sub-domain
cf.cloudlab.redhat.com	172.16.0.20	CloudForms server
satellite.cloudlab.redhat.com	172.16.0.25	Red Hat Satellite 6.1 server
rhevm.cloudlab.redhat.com	172.16.0.50	Red Hat Enterprise Virtualization Manager server
kvm.cloudlab.redhat.com	172.16.0.55	KVM hypervisor managed by Red Hat Enterprise Virtualization
esx00.cloudlab.redhat.com	172.16.0.30	ESXi hypervisor
vcenter.cloudlab.redhat.com	172.16.0.40	VMware vCenter server
osp.cloudlab.redhat.com	172.16.0.60	Red Hat OpenStack Platform server
migration.cloudlab.redhat.com	172.16.0.11	Virtual-to-Virtual Migration server

1.2. Provision Your Demo Environment

1. Log in to https://rhpds.redhat.com with your OPENTLC SSO credentials.

2. Go to Services → Catalogs → Service Catalogs.

3. Under All Services → Cloud Infrastructure Demos, select Red Hat Cloud Suite Migration Demo.

4. On the right, click Order.

5. Read all of the information on the resulting page, check the necessary box, and then click Submit.

Important

It takes about 20 minutes for your demo to load completely and become accessible, even if some of the systems are marked "Up." You will receive an email with information about how to access your demo environment. The email contains a list of hostnames, IP addresses, and your GUID; make note of them. Whenever you see GUID in the demo instructions, replace it with the GUID provided in the email. You can get real-time updates of your demo environment at https://www.opentlc.com/rhpds-status.

Tip

Be very mindful of the runtime of your demo environment! It may take you several hours to complete the demo, so you may have to extend the runtime. This is especially important in later steps, when you are building the VMs. For information on how to extend runtime and lifetime, see https://www.opentlc.com/lifecycle.

2. Getting Started

1. Once the system is running, use SSH to access your demo server using your OPENTLC login name and private SSH key.

   • Example using a Unix/Linux system:

     $ ssh -i /path/to/private_key <YOUR-OPENTLC-USERNAME>@demo-<YOUR-GUID>.rhpds.opentlc.com

2. Become root using your OPENTLC password:

   $ sudo -i

3. Establish an SSH connection to the CloudForms server and monitor automation.log:

   # ssh cf
   # tail -f /var/www/miq/vmdb/log/automation.log

   Tip	The log entries are very long, so it helps if you stretch this screen as wide as possible.

4. From a web browser, open each of the URLs below in a separate window or tab using these credentials (except when noted):

   • Username: admin

   • Password: r3dh4t1!

     Note	You must accept all of the self-signed SSL certificates.

     Tip	You can also find these URLs in the email provided when you provisioned the demo environment.

   • Red Hat Enterprise Virtualization Manager: https://rhevm-GUID.rhpds.opentlc.com

     1. Navigate to and click Administration Portal and login with: admin|r3dh4t1!|internal.

   • vCenter: https://vcenter-GUID.rhpds.opentlc.com

     1. Use the username root to log in to vCenter.

     2. Click Log in to vSphere Web Client.

        • Flash Player is required.

     3. Click VMs and Templates.

   • CloudForms: https://cf-GUID.rhpds.opentlc.com

   • OpenStack Dashboard: https://osp-GUID.rhpds.opentlc.com/dashboard

2.1. Validate the Current VMs

1. On the cf system, go to Infrastructure → Providers.

2. If you see an exclamation mark (!) in a provider, check the provider’s box, go to Configuration → Edit Selected Infrastructure Provider, and click Validate.

3. Repeat the previous step for each provider.

4. Go to Infrastructure → Providers → Virtual Machines → VMs → All VMs.

5. Make sure all four VMs show up as entities in CloudForms.

   Note	If you needed to validate providers, you may have to wait a few minutes and refresh the screen before the VMs show up.

6. Tell CloudForms to shut down (not power off) all four VMs.

3. Migrate a VM from VMware to Red Hat Enterprise Virtualization

3.1. Configure Red Hat Enterprise Virtualization as a Migration Destination

1. On the cf system, go to Infrastructure → Providers.

2. Click RHEV.

3. Select Policy → Edit Tags.

4. Select Point of Arrival and then select Rhev for the assigned value.

   • This sets this provider as an available Red Hat Enterprise Virtualization destination.

5. Select the provider_type tag and select POA for the assigned value, then click Save.

   • This sets this provider as the current point of arrival.

3.2. Configure VMware as a Migration Source

1. Navigate to the VMware provider.

2. Select Policy → Edit Tags.

3. Select provider_type and select POD for the assigned value, then click Save.

   • This sets this provider as the point of departure or source provider.

3.3. Set VM Migration Attributes

1. On the cf system, go to Services → Catalogs → Service Catalogs.

2. Under All Services → Import CSV, select Import Attributes.

3. On the right, click Order.

4. On the resulting screen, type attributes.csv in the Filename field and click Submit.

5. Monitor automation.log on the cf server. When the process is complete, continue with the next section.

   Note	If you see any errors about wp2-rhcs-cloudlab-redhat-com, you can ignore them for now because you are not exporting from Red Hat Enterprise Virtualization yet.

3.4. Set VM Migration Tags

1. On the cf system, go to Services → Catalogs → Service Catalogs.

2. Under All Services → Import CSV, select Import Tags.

3. On the right, click Order.

4. On the resulting screen, type tags.csv in the Filename field and click Submit.

5. Monitor automation.log on the cf server. When the process is complete, continue with the next section.

   Note	Continue to ignore errors about wp2-rhcs-cloudlab-redhat-com.

3.5. Check Tags and Attributes

1. Go to Infrastructure → Providers → Virtual Machines → VMs → All VMs.

2. Navigate to the mysql VM.

3. Under Custom Attributes, confirm that there is a custom attribute called ip with the value you provided in attributes.csv.

4. Under Smart Management, confirm that migrate_group is set to demo1 and Point of Arrival is set to Rhev.

3.6. Start VM Migration

1. On the cf system, go to Services → Catalogs → Service Catalogs.

2. Under All Services → Migration, select Batch_Migrate.

3. On the right, click Order.

4. For Migration Group, select demo1 and click Submit.

5. Monitor automation.log and the Red Hat Enterprise Virtualization Admin GUI closely.

   Note	It may be beneficial to open three separate sessions to the Migration server and run the following:

   # watch find /mnt

   # tail -f /mnt/migrate/ova/mysql.rhcs.cloudlab.redhat.com/*log

   # tail -f /mnt/migrate/ova/mysql.rhcs.cloudlab.redhat.com/*err

Note	It takes about 20 minutes for automation.log to show that the service has completed.

3.7. Verify VM Migration

1. Log in to the Red Hat Enterprise Virtualization Admin GUI and open the console for the mysql VM that was migrated.

2. Log in as root with the password r3dh4t1!.

3. Make sure the VM retained the IP from the attributes.csv and that it can resolve an external hostname.

4. Migrate a VM From VMware to OpenStack Platform

1. Configure OpenStack Platform as a migration destination.

   1. On the cf system, go to Clouds → Providers.

   2. Select OSP.

   3. Select Policy → Edit Tags.

   4. Select Point of Arrival and select OpenStack for the assigned value.

      • This sets this provider as an available OpenStack destination.

   5. Select provider_type and select POA for the assigned value, then click Save.

      • This sets this provider as the current point of arrival.

2. Clear the POA tag from Red Hat Enterprise Virtualization.

   1. On the cf system, go to Infrastructure → Providers.

   2. Select RHEV.

   3. Select Policy → Edit Tags.

   4. Click the Trash Can icon next to the Point of Arrival tag.

   5. Click the Trash Can icon next to the provider_type tag.

   6. Click Save.

3. Set the VM tags and attributes.

   1. Using the procedure learned before, monitor automation.log while running the Import Tags and Import Attributes catalog items again.

      Note	You can ignore the warnings from the VMs with disabled providers.

4. Migrate the VM.

   1. On the cf system, go to Services → Catalogs → Service Catalogs.

   2. Under All Services → Migration, select Batch_Migrate.

   3. On the right, click Order.

   4. For Migration Group, select demo2 then click Submit.

5. Monitor automation.log and the OpenStack Platform dashboard closely.

5. Migrate a VM From Red Hat Enterprise Virtualization to OpenStack Platform

1. Clear the POA tag from VMware.

   1. On the cf system, go to Infrastructure → Providers.

   2. Select VMware.

   3. Select Policy → Edit Tags.

   4. Click the Trash Can icon next to the Point of Arrival tag.

   5. Click the Trash Can icon next to the provider_type tag.

   6. Click Save.

2. Configure Red Hat Enterprise Virtualization to be a POD.

   1. Navigate to the RHEV provider.

   2. Click Policy → Edit Tags.

   3. Select the provider_type tag, select POD for the assigned value, and then click Save.

3. Set the VM tags and attributes.

   1. Using the procedure learned before, monitor automation.log while running the Import Tags and Import Attributes catalog items again.

      Note	You can ignore the warnings from the VMs with disabled providers.

4. Migrate the VM.

   1. On the cf system, go to Services → Catalogs → Service Catalogs.

   2. Under All Services → Migration, select Batch_Migrate.

   3. On the right, click Order.

   4. For Migration Group, select demo3 then click Submit.

5. Monitor automation.log and the OpenStack Platform dashboard closely.

6. End State

• You now have the mysql server on Red Hat Enterprise Virtualization and the two wp servers on OpenStack Platform.

• The haproxy system remains on Red Hat Enterprise Virtualization.

7. Extra Credit

• Use what you learned in this lab to migrate haproxy to OpenStack Platform.