Rehost

Prerequisites

Access to OmniDeq

In order to use the OmniDeq’s lift shift solution, first we need to have access to Cloudhedge's OmniDeq.
Open your web browser (recommended Chrome) and navigate to the 'omnideq-appliance-URL' to access OmniDeq.
Login using credentials you received from CloudHedge team.

AWS account

AWS account/s with programmatic access (Access Key, Secret Access Key)
Initializing Application Migration Service in required aws account and region.
Note that only Admin users can initialize this service. This is one time activity per region. Visit link to learn more.
Add AWS vault in OmniDeq. Refer to this page

Source server configurations

OmniDeq requirements

In case of Linux source servers,
- Verify the pre-requisistes mentioned on this page are met.
- python3,wget,make,gcc,perl,tar,gawk,rpm are installed
- Add below line in /etc/sudoers file. In below line, we have added python3 path at the end.

<ssh-user-for-omnideq-host> ALL=(ALL) NOPASSWD:/opt/.ch-tools/*/*/*, /opt/.ch-tools/*/*, /bin/mkdir, /bin/echo, /bin/chmod 755 /opt/.ch-tools/*, /bin/chmod 755 /home/<ssh-user-for-omnideq-host>/chcmd, /bin/chmod -R 755 /opt/.ch-tools, /bin/chmod -R 755 /home/<ssh-user-for-omnideq-host>/.ch-tools, /bin/chown <ssh-user-for-omnideq-host>\: /opt/.ch-tools/*, /bin/chown -R <ssh-user-for-omnideq-host>\: /home/<ssh-user-for-omnideq-host>/chcmd, /bin/chown -R <ssh-user-for-omnideq-host>\: /opt/.ch-tools, /bin/chown -R <ssh-user-for-omnideq-host>\: /home/<ssh-user-for-omnideq-host>/.ch-tools, /usr/bin/python3

In case of Windows source servers,
- Verify pre-requisites mentioned on this page are met.
- TLS 1.2 enabled
  - Use command [Net.ServicePointManager]::SecurityProtocol to know which TLS is enabled.
- DotNet 4.5 or above

NOTE : For more prerequisistes information visit the link

AWS requirements

Important network settings are needed to be done on source servers ( and at firewall level in case source server is running in air-gapped env). This mainly includes

Access to various AWS services on port TCP/443.
Access to AWS MGN service on port TCP/1500 for data sync. This AWS documentation page describes all required network settings need to be done on source servers.

Limitations

AWS MGN is regional service. It is available in regions described in this official document.
AWS MGN service has quota limits as described in this official document.

Workflow

Add VM in OmniDeq platform

To add source VM in the OmniDeq platform, login to OmniDeq
Click on Add Project. Add Name of the project(e.g. RehostVMs) of your choice, and choose preferred cloud AWS.

Add Projects

In hosts section:
- Choose the OS (Linux or Windows) type of source VM this could be Linux, Windows. [AIX is not supported].
- Enter Alias of your choice. e.g. on-premise-ubuntu1
- Select the connection type. This could be SSH or Basic in case of Linux & Basic and Kerberos in case of Windows.
- Choose an already added vault or create a new one by clicking on + Create new vault button in Choose Credentials dropdown. This page explains how to add different types of vaults.
- The username of the source VM will be auto-populated after selecting the vault. This user is used to connect to VM.
- Enter the hostname or IP address of the source VM. Make sure, this IP/Hostname should be accessible from OmniDeq.
- Enter the Port number on which OmniDeq can connect to source VM.
Add more VM’s by clicking on + Host button.

Add VMs

Finally click on Save button. This action will add a project in the OmniDeq.

Make sure OmniDeq can connect to VMs

To make sure that OmniDeq is able to connect to source VM

Select the project -> Click on Discover.
Click on the kebab menu icon of respective added host.
Select Check Connection
Click on Discover logs pane for more information while checking connection
Once check connection is successful, the window will look like as below ![Connection success]

Check prerequisites and Discover the hosts

Once, connection to vm is completed, proceed to Check prerequisistes process.
Select the vms(if required all), and click on Check prerequisites button.
This will make sure that the vms are compatible for rehosting.
If any vm fails for prerequisites, check for logs at the bottom of the screen.
It is recommended to perform discovery of the vms added for extra information of vms.
- Select the vms and click on Discover button.

Start Rehost process

After successful discovery of vms, let's start the rehost process.

Click on Transform option in the left side menu.
Click on Hosts option above.
There will be the list of vms. Select the required vm and click on Start rehosting button above.
There will be a screen to enter the target cloud details(e.g. AWS). Fill the cloud, vault and region correct and click on Rehost button.
It takes about 5-6 minutes to install the AWSReplicationInstaller agent. You can check the rehosting status column.
You can view the respective status by clicking on view(eye) icon in the last column.
Once everything is in place, you will see the vm in Ready for testing phase.

AWS launch templates modification

AWS by default creates the instances of below types
- c4
- c5
- d2
- i3
- m4
- m5
- r4
- r5
If you wish to change the instance type, login to AWS cloud and change the region accordingly.
Search for AWS Application Migration Service. Click on Launch Template option in the left side column.
Create a new template or modify existing one with unchecking the Activate instance type right-sizing option and Save.
Go back to AWS application migration service page and click on Source servers option in the left side column.
There will be list of servers which we selected for rehosting in OmniDeq.
Select the required server. Click on Launch settings tab. Note the 'Template ID' for further use. Scroll down to EC2 Launch Template section and click on Modify button.
Give the appropriate name(e.g. on-premise-ubuntu1) in 'Template version description'. Scroll down to 'Instance type' section and change the instance type as required.
- Optional - Scroll down to 'Network settings' section, click on 'Advanced network configuration' and select Enable option in 'Auto-assign public IP' drop-down.
Click on 'Create template version' button to the right.
Once completed, search for EC2 service and go to EC2 dashboard page.
Click on the 'Launch Templates' option on the left side column and click on the template id which we copied earlier. You can get that id again from source servers page.
Scroll down to 'Launch template version details' section and click on 'Actions' button to the right. Select Set deafult version option.
Click on 'Template version' and select the newly created template version. You can see the name given earlier given while modifying launch template.

Launch Test Instance

Go back to OmniDeq, wait for the status to be Ready for testing. It takes time depending upon the size of vm to be migrated.
Once Replication stage is completed, click on the drop-down box beside 'Actions' button and select Launch test instance.
The phase will change to Test in progress.
You can view on AWS -> EC2 -> Instances page that the replication server, conversion server are created which will make the test instance to be launched.
After the 'Ready for testing' phase is completed in OmniDeq, you can see the details of newly created test instance with source vm name in 'Testing status details' section.
- It can be also verified in AWS -> EC2 -> Instances
- Try connecting via ssh to the test instance and do testing.
In OmniDeq, once testing is done and verified, click on Mark as Ready for Cutover option in the the drop-down box beside 'Actions' button.
- At this stage, the test instance will be terminated.
Once completed, select the Launch cutover instances option in the drop-down box.
- At this stage, new instance will be created.
After all checks with newly created instance, click on Finalize cutover option in the drop-down box.
All the stages will be completed and the source vm is migrated and rehosted to AWS cloud.