h1. Request Details
h2. Background
Design review : https://docs.google.com/document/d/1HH7L2aVou8khyq5ljr30V_0GtfwRdZTo6Y_351bWfXU/edit#
Because we are separating the owner of provider and canonical data into separate services, we will need to migrate the old data from their databases into the new databases.
h2. Purpose
Migrate old data from acontent-mongod, asset-mongod, hotel-mongod, hdata-mongod, to the new axtpcnt-mongod. This is a one-time migration cluster. After the migration is done, axtpmig will be decommissioned wholly.
h2. Impact
By having a separate service for the migration process, we will not affect the main services in their original function. And when the migration is completed, we can just decommission axtpmig altogether
h2. Risk
An small increase in axtpcnt-mongod load when the migration.
h2. Resources
h3. EC2
h4. Configuration
{code}
count = "1"
instance_type = "r4.large"
ebs_optimized = "false"
disable_api_termination = "false"
root_block_device = {
volume_type = "gp2"
volume_size = "8"
delete_on_termination = "true"
}
tags = {
Service = "axtpmig"
Cluster = "axtpmig-app"
ProductDomain = "axt"
Application = "java-7"
Environment = "production"
Description = "Accom Supply Provider Migrator"
}
{code}
h3. Connectivity
h4. Rules
https://docs.google.com/spreadsheets/d/1hms_nBD3tXn2UYhGuoNjQ9XJ4Gxk_RVj3fXSq542ip0/edit#gid=0
[^connectivity.csv]