- Matilda Migrate Architecture
- Matilda Migrate Installation Requirements
- Matilda Migrate Installation
- RACI Matrix
- Ports Reference
Matilda Migrate Architecture #
Matilda Migrate Architecture
Matilda Migrate Installation Requirements #
Access Requirements #
The Matilda SME must have RDP/VDI/VPN access to connect client’s network and must be able to connect to the Matilda instance using SSH clients, such as putty.
Server OS Requirements #
- RHEL 7.8, 7.9
- CentOS 7.8, 7.9
- Ubuntu 20.04, 22.04
Sever Compute Requirements (Single VM) #
- vCPU: 4
- Memory: 16 GB
- Storage: 350 GB
- Number of instances: 1
File System Requirements #
- Root (/): 30 GB
- Var(/var): 70 GB
- Matilda Migrate(/matilda): 250 GB
Ports to be Open on Matilda Server #
The following ports must be open:
- Ports for Inbound traffic: 22, 443, 8443
- Ports for Outbound traffic: 22, 5985/5986, 445, 1466, 1521, 3306, 27017, Cloud Provider APIs
See Ports Reference section for more information.
Access to External URLs #
The Matilda Migrate server must be able to access the following external URLs to set up Matilda Migrate.
The API endpoints of the target cloud provider must be accessible from the Matilda Migrate instance.
If you are unable to download the docker images, use the following policies in your S3 bucket:
Installation Prerequisites – Linux commands #
SSH into the instance and switch to root to execute the following commands:
|Packages||Operating System -RHEL/Centos||Operating System -Ubuntu|
|curl||yum install -y curl||apt-get install -y curl|
|git||yum install -y git||apt-get install -y git|
|host||yum install -y host||apt-get install -y host|
|nc||yum install -y nc||apt-get install -y nc|
|openssl||yum install -y openssl||apt-get install -y openssl|
|unzip||yum install -y unzip||apt-get install -y unzip|
To install the prerequisite Linux commands on an RHEL instance, install the following packages:
# yum install -y git curl unzip bind-utils nmap-ncat openssl
To install the prerequisite Linux commands on an Ubuntu instance, install the following packages:
# apt-get install -y git curl unzip bind9-utils nmap ncat openssl
Steps for Running a Precheck on the Server #
The following steps must be completed before Matilda Migrate can be installed.
- Clone the below repository as root. The Matilda team will provide the necessary credentials to clone the git repository.
# git clone https://bitbucket.org/matildaapp/matilda_prechecks.git
- Change the directory to matilda_prechecks.
# cd matilda_prechecks
- Create a directory named /matilda and mount additional storage (250GB).
# mkdir /matilda
- Run the binary script of matilda_precheck.sh and fix the errors.
Note: The precheck script will fail in any one of the following cases:
- If the VM requirements (CPU/Memory/FileSystem Size) are not met.
- If the installation prerequisites commands list is not executed prior to the precheck.
- If the mount point /matilda is not created.
If the prechecks complete successfully, Matilda Migrate can be installed successfully.
Matilda Migrate Installation #
This guide provides the steps to install Matilda Migrate in a Kubernetes cluster single node environment.
Installation Steps #
The preceding Matilda Migrate prerequisites must be properly performed before proceeding into the installation steps below.
Note: Contact the Matilda support team 24 hours prior to installation for installation credentials and IP whitelisting. These credentials are available for only 24 hours and are not transferable.
- Download the installation git repository from the following location:
# git clone https://bitbucket.org/matildaapp/mdeploy_migrate.git
- Change the directory to mdeploy_migrate and set executable permissions to the installation script using the following commands:
# cd mdeploy_migrate
# chmod +x matilda_install.sh
- Update the config file in the installation directory as specified below. Consult the Matilda team for the necessary details, such as the username, password, and email.
# vim config USERNAME==<Matilda team to share> PASSWORD=<Matilda team to share> TLS_KEY_PATH=<Client to provide> TLS_CRT_PATH=<Client to provide>
Note: Configuration updates are mandatory and without proper configuration, installation will not proceed.
- Run the installation script.
External Identity Provider Integration Steps (Optional) #
Please refer the following documentation for OIDC and SAML integration https://matildacloud.atlassian.net/wiki/spaces/MM/pages/2204106753/External+Identity
Matilda Application URLs #
Migrate URL: http://<dns_name>
Logins: Single sign on email / local login ID
Password: < Admin password >
The Matilda team will share the local admin credentials.
Note: A user account with the root permissions should be created on the server. Enable switching to root context with no password authentication on Matilda Server.
RACI Matrix #
|Matilda Migrate VM provisioning||Client|
|Matilda SME On Boarding with required user account privileges||Client|
|Service account creation/validation with required privileges for Windows & Linux as requested in the document||Client|
|DB account creation with required privileges for ORACLE/MSSQL/MariaDB/MySQL/MongoDB Servers||Client|
|VPN/VDI/RDP Access and Matilda SNE Access to Matilda Migrate VM||Client|
|Set up of Matilda Migrate Platform on the provisioned VM||Matilda|
|Pre-check and validation of Matilda deployment||Matilda|
|Promote applications from Matilda Discovery to Matilda Migrate||Matilda and Client|
|Create Templates and standardize the cloud resources onboarding process||Matilda and Client|
|Requirement for additional plugins – Matilda team review the requirements and accommodate as part of enhancements||Matilda and Client|
|Map templates to discovered applications and create workflows and waves||Matilda and Client|
Ports Reference #
The following ports are to be open on the Matilda Server:
|Incoming to Matilda Server||Port 22 is to connect to server to deploy the tool
Ports 443 & 8443 are useful to run the Matilda Platform in customer environment and accessible Matilda Migrate tool from VDI/VPN/Customer Internal network
Custom Database Ports
|Outgoing from Matilda Server||SNMP: 161/162 (Optional)
Linux/Unix – SSH: 22
Windows – WinRM: 5985/5986 SMB: 445
Oracle DB: 1521
Cloud Services: HTTPS/443
Matilda Cloud support is offered by email during working hours Monday-Friday. Please contact email@example.com for assistance.