Migrate from GCP to On Premise

In this article

• What is On-Premise?
• What is Colocation?
• Prepare Your On-Premise Cloud
• What is Hosted Private Cloud?
• Migrate from GCP to OpenStack
• GCP Pricing Comparison
• Final Thoughts

Considering a shift away from Google Cloud Platform (GCP)? While GCP is undeniably a major player in the cloud computing scene, the market is brimming with alternative solutions that might offer better value for your investment. With the increasing availability of cost-effective options, you might be questioning whether GCP aligns seamlessly with your current needs.

Every cloud platform, including GCP, has its strengths and weaknesses. So before committing to staying or transitioning it’s essential to thoroughly evaluate various options to ensure that your cloud caters to your requirements effectively.

Lately, organizations have been feeling the strain of run away cloud bills. Faced with unpredictable cloud bills and the limited control over their clouds, many organizations are looking to regain control of their infrastructure. This new wave of thought is making on-premise (on-prem) private clouds top of mind again.

Let’s explore the cloud landscape and see if moving your workloads from public cloud providers like GCP to on-prem is the best solution for your organization and how you can efficiently make this transition.

What is On-Premise?

An “on-premises cloud” or traditional private cloud is a cloud computing environment that an organization builds and manages for themselves within its own physical data centers. On-prem cloud solutions offer the benefits of cloud computing while maintaining control and security.

What is Colocation?

Modern day on-prem has evolved into a colocation model. Organizations seeking to build their private data centers no longer need to have their own physical infrastructure, they can rent colocation space within an existing data center. Colocation space significantly reduces the real estate, building customization, and physical security costs that an organization seeking a private cloud will incur.

Clouds can be built in a colocation cage provided by a data center, using hardware that you have either purchased or leased.

Having a dedicated space will allow for regular visits from your in-house team, external specialists, and assistance from the data center’s on-site personnel known as “smart hands.” There is still a significant time investment required for setting up your cloud, including acquiring hardware, setting up racks, deploying, and configuring your cloud environment.

For a clearer understanding of the migration choices from Google Cloud Platform (GCP) to on-premise or alternative cloud solutions, let’s examine this table created by Todd Robinson, the President of OpenMetal. This table serves as a helpful resource to help organizations understand the various modern options available for deploying your cloud infrastructure, startup time, cost, and risks associated with each model. 

For a more detailed coverage, see our blog on Cloud Deployment Models

Prepare Your On-Premise Cloud

1. For both on-premises and colocation you will need to buy or leases your own servers.
2. Once you receive your servers, you will need to rack them in your data center and set up the necessary networking for IPMI and configure the “front LAN” and “back LAN”. You should opt for a limited number of switches with well-designed VLANs to minimize costs, unless the scale of your on-premise infrastructure justifies additional expenses.
3. Next you will need to automate your hardware management with things like IPMI, PXE booting, or OpenStack Ironic, or manually configure hardware that is not suitable for automation.
4. Next, you turn the hardware into a cloud with systems like OpenStack, Ceph, Minio, CloudStack, MaaS, VMWare, Nutanix, OpenShift/OKD, Rancher and Longhorn, etc.
5. All modern systems have decent APIs – we recommend OpenStack ourselves of course – but after the above steps you will have a set of APIs or GUIs for self service resource deployment and for migration systems to talk to when automating the moves.

If you are going down this path we encourage you to still use OpenStack and check out our How to Build a Private Cloud on OpenStack article. Please bear in mind that this can be a tedious and time consuming process. Maybe you don’t have the in house expertise required or can’t have your engineering team distracted for long periods to set up and maintain your cloud.

If process of building your own cloud is more than what you are willing to take on, you can alternately move your GCP workloads to a hosted private cloud.

What is a Hosted Private Cloud?

Hosted private clouds are exclusive cloud solutions hosted on dedicated servers, providing users with root-level access for customization. Similar to public clouds, they offer rapid deployment and scalability, enabling users to adjust resources quickly.

OpenMetal, utilizing OpenStack as its foundation, delivers a Cloud Core consisting of three configured servers. This infrastructure leverages OpenStack and Ceph, offering diverse services such as Compute/VMs, Block Storage, software-defined networking, and Kubernetes clusters. The hosted private clouds are maintained by OpenMetal engineers, freeing users to focus on tasks like product development. With an API-first approach, infrastructure utilization is simplified through interfaces like command-line and graphical interfaces. This design combines the benefits of traditional and public clouds, providing a hassle-free cloud experience for customers.

Migrate from GCP to OpenStack

Since we know OpenStack the best and often help customers move from GCP to OpenStack, here is a useful chart comparing the services between the two cloud systems. Other major cloud systems all cover the most popular services and we have additional pages on those versus OpenStack.

Pricing Comparison GCP to OpenMetal