Spring Boot Petclinic application is a Java application built with Spring Boot and Maven.

Spring Boot and Vaadin FlowCRM is a sample Java CRM application built with Spring Boot, Vaadin and Maven.

Apache2 HTTPD is one of the most common and widely used open source HTTP Servers and is commonly used to front Java applications running on Tomcat and act as a reverse proxy to the upstream Tomcat instances.

In this tutorial you will deploy the two applications into a Tomcat server running on a Google Compute Engine (GCE) VM and connect them to a MySQL database running on a GCE VM. You will also deploy the Apache2 HTTPD server on the Tomcat GCE VM and configure it to reverse proxy requests to the applications running on the Tomcat instance.

You'll then use Migrate to Containers to migrate the two applications to run each in a Tomcat app container on a Google Kubernetes Engine (GKE) cluster and generate Day2 artifacts to support modern CI/CD operations for your application. You will also migrate the MySQL database into a StatefulSt and persist it's data on a Persistent Volume Claim and lastly, you'll create an Ingress to externally expose the two applications.

In this tutorial you’ll do the following:

• Prepare your Google Cloud environment
• Create a MySQL Ubuntu VM on GCE and prepare the Petclinic and FlowCRM databases
• Build and deploy Petclinic application into Tomcat on a GCE vm
• Build and deploy FlowCRM application into Tomcat on the above GCE vm
• Install and Configure Apache2 HTTPD server on the above GCE vm
• Install and configure Migrate to Containers
• Qualify the workloads for migration using the Migration Center discovery client CLI (mcdc CLI)
• Migrate Petclinic and FlowCRM databases vm to a container with persistent data
• Migrate Petclinic application to a Tomcat container
• Migrate FlowCRM application to a Tomcat container
• Deploy the migrated database and applications to your GKE cluster
• Configure an Ingress to expose your migrated applications
• Clean up by deleting the project

For this reference guide, you need a Google Cloud project. You can create a new one, or select a project you already created:

1. Select or create a Google Cloud project.
   GO TO THE PROJECT SELECTOR PAGE

2. Enable billing for your project.
   ENABLE BILLING

3. Enable the Service Management API, Service Control API, Cloud Resource Manager API, Compute Engine API, Kubernetes Engine API, Google Container Registry API, Cloud Build API, Cloud Source Repositories API.
   ENABLE THE APIS

Your migration journey consist of a number of steps:

1. Prepare - In this step you will prepare your environment by installing MySQL and Tomcat VMs, building and deploying the application and then installing Migrate to Containers.
2. Assess - In the assess step, you will run the Migration Center discovery client CLI and assess whether or not your MySQL and Tomcat workloads are good fit for containerization.
3. Migrate your MySQL - In the first migrate step you will migrate your MySQL VM into a container and generate Day2 artifacts which can later be used in modern CI/CD pipelines.
4. Migrate your Tomcat applications - In the second migrate step you will migrate your Tomcat applications into containers and generate Day2 artifacts which can later be used in modern CI/CD pipelines.
5. Deploy - In the deploy step you will deploy your migrated workloads into a GKE cluster and verify that your applications are working as expected.
6. Optimize - In the optimize step you will configure an Ingress to map and expose your migrated applications.

The simplest way to avoid any unexpected billing charges is to delete your GCP project. You can do so by running the command below in cloud shell:

gcloud projects delete $PROJECT_ID