Stay organized with collections Save and categorize content based on your preferences.

Build a Tomcat container image

When you generate artificats for Tomcat workloads, Migrate to Containers creates a build.sh script. You then use this script to build the deployment container image.

Before you begin

This topic assumes that you've already:

Review the artifacts

Review the artifacts before building the deployable container image. Run the following command:

migctl migration get-artifacts my-migration

Migrate to Containers makes a corresponding nested directory according to your migration plan for each of the server images. These nested directories include image artifacts for building and deploying an image. The command above allows you to download the generated container artifacts in this nested directory.

Included in each directory you can find multiple artifacts:

  • the build.sh file that you can use to build the container image for the Tomcat server
  • the deployment_spec.yaml file that you use to deploy the container image
  • the cloudbuild.yaml file that you can use to rebuild the image later as part of a CI/CD pipeline
  • the volumes.yaml file which contains a breakdown of your migrated data volumes

  • the secrets.yaml file that contains the sensitive data collected by the migration, if requested by the user

    For more information about verifying your migration artifacts, see Step 9: Verify volumes.yaml below.

(Optional) Verify volumes.yaml

One of the artifacts that Migrate to Containers generates upon completion of a migration is the volumes.yaml file.

Your volumes.yaml file contains information about the PVCs, and PVs that data was copied into as part of the data migration. You can choose to use this information to modify the migrated workload. Do this before you deploy workload in order to make the copied data accessible.

The format of the volumes.yaml file is shown in the following:

    volumes:
           deployment pvc name:
             pvc:
               full pvc yaml
             pv:
               full pvc yaml

For more information about defining a PVC or PV yaml file, see the Kubernetes documentation.

For more information about defining your data volumes, see the Customizing your data migration configuration section.

Build the container image

You can build the container image using build.sh or Skaffold. Skaffold allows you to build and deploy in the same command, and is typically easier to use. If you don't want to use Skaffold, you can use build.sh.

To build using Skaffold, see Build and deploy multiple images using Skaffold.

Build the container image using build.sh

  1. Use the build.sh file created in the migration artifacts to build the container image for your Tomcat server.

    1. Change to the directory where the generated artifacts for your Tomcat image are.

      For example, to change to the directory for a Tomcat server named latest and an image named app, run the following command:

      cd latest/app

    2. Set your Google Cloud Project ID and image version:

      export PROJECT_ID=my_project VERSION=latest

    3. Run the build.sh script to build your container image and upload it to the Container Registry:

      bash ./build.sh

What's next

Linux

Migrate

  1. Add a migration source.
  2. Create a migration plan.
  3. Migrate data.
  4. Customize your migration plan.
  5. Execute the migration.
  6. Monitor a migration.
  7. Delete a migration.

Deploy

  1. Review generated artifacts.
  2. Configure logging.
  3. Mounting external volumes.
  4. Deploy a workload to a target cluster.
  5. Deploy migrated VMs.
  6. Post-migration image updates.
  7. Monitor migrated workload.
  8. Test your migrate app and validate the migration.

Windows

Migrate

  1. Add a migration source.
  2. Create a migration plan.
  3. Customize your migration plan.
  4. Execute the migration.
  5. Monitor the migration.
  6. Build a Windows container image.
  7. Delete a migration.

Deploy

  1. Deploy a workload to a target cluster.
  2. Deploy migrated VMs.
  3. Monitor migrated workload.
  4. Test your migrate app and validate the migration.

Tomcat

Migrate

  1. Add a migration source.
  2. Create a migration.
  3. Migrate data.
  4. Customize your migration plan.
  5. Execute the migration.
  6. Monitor the migration.
  7. Build a Tomcat container image.
  8. Delete a migration.

Deploy

  1. Deploy a workload to a target cluster.
  2. Deploy migrated VMs.
  3. Monitor migrated workload.
  4. Test your migrate app and validate the migration.

WebSphere

Migrate

  1. Migration overview.
  2. Requirements.
  3. Before you begin.
  4. Add a migration source.
  5. Create a migration plan.
  6. Migrate data.
  7. Customize the migration plan.
  8. Execute the migration.
  9. Monitor the migration.
  10. Build an app container image.
  11. Deploy an app container to a target cluster.
  12. Delete a migration.
  13. Troubleshooting.

Deploy

  1. Deploy a workload to a target cluster.
  2. Deploy migrated VMs.
  3. Monitor migrated workload.
  4. Test your migrate app and validate the migration.

JBoss

Migrate

  1. Add a migration source.
  2. Create a migration.
  3. Migrate data.
  4. Customize your migration plan.
  5. Execute the migration.
  6. Monitor the migration.
  7. Build a JBoss container image.
  8. Delete a migration.

Deploy

  1. Deploy a workload to a target cluster.
  2. Deploy migrated VMs.
  3. Monitor migrated workload.
  4. Test your migrate app and validate the migration.

Apache

Migrate

  1. Add a migration source.
  2. Create a migration.
  3. Migrate data.
  4. Customize your migration plan.
  5. Execute the migration.
  6. Monitor the migration.
  7. Build an Apache container image.
  8. Delete a migration.

Deploy

  1. Deploy a workload to a target cluster.
  2. Deploy migrated VMs.
  3. Monitor migrated workload.
  4. Test your migrate app and validate the migration.

WordPress

Migrate

  1. Add a migration source.
  2. Create a migration.
  3. Customize your migration plan.
  4. Migrate data.
  5. Execute the migration.
  6. Monitor the migration.
  7. Build a WordPress container image.
  8. Delete a migration.

Deploy

  1. Deploy a workload to a target cluster.
  2. Deploy migrated VMs.
  3. Monitor migrated workload.
  4. Test your migrate app and validate the migration.