Do you think IIT Guwahati certified course can help you in your career?
Introduction 📝
In this blog, we will discuss the process of migrating for Compute Engine. Migration plays an important role in the compute engine, sometimes we need to shift from one service to another for that we need to know the process of migration of compute engine. In this blog, we are going to discuss the process of migrating from different services like AWS, and Azure to GCP.
About Migrate for Compute Engine🎛️
Migrate for Compute Engine gets enterprise apps up and operating in Google Cloud in minutes, while data migrates in the background invisibly. Enterprises can use Migrate for Compute Engine to validate, operate, and migrate apps onto Google Cloud without rewriting them, changing the image, or changing management processes.
See the Google Cloud reference architecture for additional details on the Migrate for Compute Engine solution design, features, and terminology.
Review the migration requirements
Review the migration requirements from your source platform.
Set up a migration environment
Prior to migrating, you set up a migration environment that consists of network configuration, a migration manager to handle migration, source platform configuration, and Cloud Extensions acting as a conduit for storing data on the destination side.
You can manually import and configure discs if you need to make intricate adjustments or if your source discs are in a format that the import command does not allow.
Importing machine images. The settings, metadata, permissions, and data from one or more discs needed to create a virtual machine instance are all stored in a machine image, a resource in Compute Engine.
For building machine images from virtual appliances, this technique works best.
Overview of migrating from AWS to GCP ⚙️
The general procedures needed to transfer virtual machines (VMs) from AWS EC2 to Google Cloud using Google Cloud Migrate for Compute Engine are described in this overview (formerly Velostrata).
GCP requirements
You must create IAM (Identity and Access Management) permissions before starting a transfer to Google Cloud.
Setting up a VPN plan
Set up a VPN plan to establish a secure connection between AWS and Google Cloud. One method is to use Terraform to create one.
Configure AWS Networks
For comprehensive information on the firewall, routing, and network tag concerns for your Migrate for Compute Engine deployment, see Network Access Requirements.
Make IAM credentials for AWS.
Establish IAM groups and credentials to allow the Compute Engine Migration to connect to AWS.
Configure the Compute Engine Manager migration
The Migrate for Compute Engine Manager offers a web UI and manages Google Cloud migration processes. Set it up so it will go on.
To migrate for Compute Engine Manager, upload the AWS IAM credentials.
Utilizing your AWS IAM credentials, generate Cloud Details on your Migrate for Compute Engine Manager.
Establish Cloud Extensions
Create Cloud Extensions for your migration once the Migrate for Compute Engine Manager has been configured.
Prepare your Linux virtual machines.
Install the Migrate for Compute Engine package to adapt your Linux virtual machines for Google Cloud if you are migrating them.
Make a copy for testing
To do a test migration on a specific VM, you can build a test clone, after which you can verify the moved VM. Test clones are copies of virtual machines that don't use real data from the original platform.
Move a large number of virtual machines
VM groups are grouped together into waves by Migrate for Compute Engine. Create runbooks that contain collections of virtual machines and start your migration after understanding the interdependence of your apps.
Overview of migrating from Azure to GCP⚙️
The general procedures needed to transfer virtual machines (VMs) from Microsoft Azure to Google Cloud using Google Cloud Migrate for Compute Engine are described in this overview (formerly Velostrata).
Set up the migration's source and destination.
Create GCP as a destination for migration. You must create Identity and Access Management permissions before starting a transfer to Google Cloud.
For communication between the migration source and destination, set up a VPN. Prepare and establish a safe connection between Google Cloud and Azure. Utilizing this tutorial is one approach to achieving this.
Establish network access. For comprehensive information on the firewall, routing, and network tag concerns for your Migrate for Compute Engine deployment, see Network Access Requirements.
Create the Azure credentials necessary for Migrate for Compute Engine to connect to Azure in the Migrate for Compute Engine Manager.
Configure the Compute Engine Manager Migrate. Changing for Computer.
Configure Cloud Extensions. Create Cloud Extensions for your migration once the Migrate for Compute Engine Manager has been configured.
To do a test migration, create a test clone for a specific VM, then verify the moved VM. Test clones are copies of virtual machines that don't use real data from the original platform.
Prepare your Linux virtual machines. Install the Migrate for Compute Engine package to adapt your Linux virtual machines for Google Cloud if you are migrating them.
Overview of on-premises to GCP migration 🌐
The general procedures needed to transfer virtual machines from vSphere to Google Cloud using Google Cloud Migrate for Compute Engine are described in this overview (formerly Velostrata).
GCP requirements
It is necessary to create Identity and Access Management permissions before starting a transfer to Google Cloud.
Set up a VPN plan
For a safe connection between your on-premises data center and Google Cloud, set up a VPN plan. You can create a secure connection using either Cloud VPN or Cloud Interconnect.
Firewall settings on Google Cloud
Create firewall rules for your on-premises, AWS, and Azure environments as well as Google Cloud.
Configure the Compute Engine Manager migration
A web UI is offered and migration activities from Google Cloud are managed by the Migrate for Compute Engine Manager on Google Cloud. To continue, configure the Google Cloud migration for Compute Engine Manager.
Establish Cloud Extensions
Make Cloud Extensions for your migration once the Manager and Backend have been configured.
Prepare your Linux virtual machines
Install the Migrate for Compute Engine package to adapt your Linux virtual machines for Google Cloud if you are migrating them.
Move one virtual machine
You may now use the vSphere console to run a virtual machine in the cloud.
Move a large number of virtual machines
Waves are used by Migrate for Compute Engine to group together VMs. Create runbooks that contain groups of virtual machines after understanding the requirements of your apps, then start your migration
Deploying the Migrate for Compute Engine Backend 📝
Utilizing Cloud Extensions, the virtual appliance Migrate for Compute Engine On-Premises Backend streams or migrates VM discs from your on-premises data center to Google Cloud.
A vCenter plug-in that is optionally included with the Migrate for Compute Engine On-Premises Backend virtual appliance offers migration functions within the vCenter user interface. The plug-in can be helpful if you wish to use the vCenter user interface or move virtual machines one at a time. However, the Migrate for Compute Engine Manager, which supports migrating VMs in batches with waves, can be used to accomplish migrations.
Sizing a VM for the Compute Engine Backend Migration
Migration Size of Compute Engine
Resources
If Size of Compute Engine <=100 concurrent migrating VMs
2 vCPU, 4GB RAM
If Size of Compute Engine>100 concurrent migrating VMs
4 vCPU, 8GB RAM
Setting up the Migrate for Compute Engine Backend for deployment
Let’s see the deploying steps in details for migration of Compute Engine Backend:
Visit the Downloads page to access the Migrate for Compute Engine Backend OVA file. With the help of Migrate for Compute Engine Backend sha256, which is accessible from the Downloads page, you can check the files' consistency.
Access vSphere by using the Flash Web Client.
Deploy OVF Template can be chosen by right-clicking a parent object of one of the VMs that needs to be moved.
Choose the OVA file titled "Migrate for Compute Engine."
In your vSphere datacenter, select the Host/Cluster where the Migrate for Compute Engine Backend will run.
Then click Next after choosing a disc format.
Choose the network details that will house the Compute Engine Backend migration. Choose Next.|
Extend the section titled "Migrate for Compute Engine Backend Configuration."
In Velostrata Backend Token, paste the token you copied from the Migrate for Compute Engine Manager on Google Cloud. This is the token that you copied from the Configure logging from Migrate for Compute Engine Manager process while configuring the migration manager.
Enter and confirm a password for the admin user on the Migrate for Compute Engine Backend. After installation, the passwd command should be used to update the password by logging into the Migrate for Compute Engine Backend through SSH as admin.
Expand the section titled "Networking Properties." Type in the Virtual Appliance's hostname. To migrate for Compute Engine Backend, enter a static IP address, Netmask, default gateway, and DNS server. You can alter these settings whenever you choose, but you must restart the Virtual Appliance for the modifications to take effect.
Fill in the HTTP Proxy field if you wish to utilize an HTTP proxy for metrics and log uploads to Google Cloud's operations suite.
To access Google Cloud subnets if your VPN connection is not set up with dynamic routing, enter the Static network route. The address has the following format: x.x.x.x/x y.y.y.y, where y.y.y.y is the on-premises VPN Gateway IP address and x.x.x.x/x is the Google Cloud VPC network address in CIDR format.
Review the Ready to complete page after clicking Next.
To finish, click. The job to deploy an OVF template emerges.
You must configure your Google Cloud organization before transferring your applications with Google Cloud Migrate for Compute Engine (formerly Velostrata). Migrate for Compute Engine may control the migration and connect with the other concerned components thanks to this setup.
The configuration of Google Cloud includes:
Establishing a Google Cloud organization, account, and infrastructure project, along with project rights for Migrate for Compute Engine's internal infrastructure.
Establishing networks on Google Cloud to enable communication between elements of your migration (such as Migrate for Compute Engine, Google Cloud, and the source environment from which you are migrating) across firewalls over Google Cloud Virtual Private Cloud.
Setting rights for Migrate for Compute Engine to be able to generate resources and control APIs needed during the migration by creating Google Cloud roles and service accounts via Cloud Shell.
Setting up a Google Cloud account, organization, and infrastructure project
To migrate to Google Cloud, you require a Google Cloud organization. Assigning rights will enable a Migrate for Compute Engine script to set up GCP with roles and service accounts after you have an organization. To host the Migrate for Compute Engine Manager, you must create a Google Cloud infrastructure project.
Log in to the Google Cloud console. You can create an account if you don't already have one by signing up.
See Creating and administering organizations for information on how to start one. Determine a resource hierarchy for your Google Cloud landing zone for additional details.
Give your administrator, who controls the account and role creation script, the following permissions:
Organization Role Administrator
Organization Administrator
Compute Admin
(Project) Owner
See the IAM Overview for additional details on IAM concepts like Google Cloud accounts, service accounts, and roles.
To host the infrastructure for Migrate for Compute Engine on Google Cloud, create a Google Cloud project. We'll refer to this project as the infrastructure project for the rest of this document.
Setting up network
Before migrations for Compute Engine can be finished, particular networking rules must be set up. Compute Engine leverages Google Cloud Virtual Private Cloud networks and VPN connectivity to your source environment. See network access requirements for comprehensive information on the firewall, routing, and network tagging for your deployment.
The network configuration chores presuppose that you are already familiar with Virtual Private Cloud firewall rules and that you have a Google Cloud Virtual Private Cloud. Visit Google Cloud Virtual Private Cloud for additional details.
Creating service accounts
You must set up service accounts with the required Google Cloud roles so that Migrate for Compute Engine can handle the Cloud Storage API and generate Google Cloud resources.
Except in cases when you'll be transferring into numerous Google Cloud projects, the service account needs to be set up in the infrastructure project. In that situation, you construct the Infrastructure Project's various roles and service accounts while also creating the Migrate for Compute Engine Manager role at the organizational level.
Create the service accounts using either:
The Google Cloud console as part of Configuring the migration manager (recommended)
The gcloud command
Frequently Asked Question❓
What is Google Cloud API?
You can use cloud APIs to automate workflows in the language of your choice. REST calls or client libraries are written in well-known programming languages that can be used with these cloud APIs.
What is Google Compute Engine?
Google Compute Engine offers a scalable number of virtual machines (VMs) to act as sizable compute clusters. GCE can be controlled using a web console, command line interface, or RESTful application program interface (API).
What are the features of Google Compute Engine?
The compute engine contains many features like Cloud storage, Global load balancing, Global load balancing, Operating system (OS) support, and many more.
What is Google Compute Engine used for?
The Google infrastructure can be used to build and run virtual machines using Compute Engine, a customized compute service. A Virtual Machine (VM) that satisfies your requirements can be created.
What is Compute Engine instance?
Google's public Linux and Windows Server images as well as privately created custom images that you can import from your current systems can both be operated on Compute Engine instances.
Conclusion ✉️
In this article, we have extensively discussed the Migrate for Compute Engine in the Google cloud project. If you would like to learn more, check out our articles on
34+ registered 
