Skip to main content
All CollectionsCloud Maker Enterprise Server
Cloud Maker CMES v1.0 to v2.0 Migration
Cloud Maker CMES v1.0 to v2.0 Migration
Nick Smith avatar
Written by Nick Smith
Updated over a week ago

Overview

This article provides updated steps for migrating from Cloud Maker Enterprise Server (CMES) version 1.0 to version 2.0, focusing on the latest constraints, prerequisites, and processes.

Constraints

  • Region Requirement: Both v1.0 and v2.0 of CMES must be in the same geographical region.

Prerequisites

  1. Deploy a new v2.0 CMES appliance by following the install user guide: https://help.cloudmaker.ai/en/articles/8464593

  2. Create a Jump Box: Provision an Ubuntu Linux server LTS, ensuring no Public IP is assigned.

  3. Create Bastion: Establish a secure connection to the JumpBox.

  4. Configure NSG Inbound Rule on VM Subnet NSG:

    • Source IP: Bastion Subnet Address Prefix (10.0.0.0/16).

    • Source Port: * (All).

    • Destination IP: JumpBox IP (10.0.0.8).

    • Destination Port: 22 (SSH).

    • Protocol: TCP.

    • Priority: 1040.

  5. Add the Jump Box to the VM Application Security Group.

  6. Add Source CMES Managed Identity to the JumpBox and record the client ID.

  7. Add Destination CMES Managed Identity to the JumpBox and record the client ID.

  8. External IP for the CMES v1.0 Postgres Server.

    1. Ping <dbserver>.postgres.database.azure.com on your local machine to obtain the public IP address. Please be sure to note this down for use in the migration.

  9. Obtain the migration scripts from your Cloud Maker support representative.

Migration Process

  1. Log on to the Jump Box using Azure Bastion configured in the pre-requisites.

  2. Prepare the Secrets Migration Script:

    • Run the following command on the command prompt vim migrate_secrets.py.

    • In VIM enter paste mode by typing: :set paste.

    • Press I to start insert mode.

    • Paste the migrate_secrets script provided in the pre-requisites.

    • Exit insert mode: Press Esc.

    • Save and exit by typing: :wq.

  3. Prepare the Main Migration Script:

    • Run the following command on the command prompt vim migrate.sh.

    • In VIM enter paste mode by typing: :set paste.

    • Press I to start insert mode.

    • Paste the migrate script provided in the pre-requisites.

    • Exit insert mode: Press Esc.

    • Save and exit by typing: :wq.

    • Make the script executable by typing: chmod +x migrate.sh.

  4. Execute the Migration:

    • Run the migration script by typing: ./migrate.sh.

  5. You will be guided through the migration steps and will be required to enter various information such as Key Vault, Storage Account and Database names, as well as supplying the admin username for your Postgres database.

Clean Up

  1. Remove Bastion: Dismantle the Bastion setup used for secure connection.

  2. Delete JumpBox: Remove the JumpBox along with its Network Interface Card (NIC) and Disk.

  3. Once migration is complete and the new CMES v2.0 has been tested and verified. You may delete your CMES v1.0.

Additional Notes

  • It is crucial to adhere to the sequence of steps as outlined to ensure a smooth and secure migration.

  • Keep backups of all critical data before starting the migration process.

  • Verify connectivity and functionality post-migration to ensure the integrity of the migrated system.

This guide is designed to ensure a comprehensive and secure migration process from CMES v1.0 to v2.0, aligning with the latest standards and practices.

Did this answer your question?