MCP Migration & DB Cleanup

[aboydnw]

Environments

IMPACT has three environments in MCP: production, test, and dev

• We already use the production environment, we want to keep this. We want this to appear on the primary URL that UAH is currently on, https://impact.earthdata.nasa.gov/apt/
• We would like to use the test environment, right now it is an empty shell that has never been deployed to
• We probably don't need the dev environment

Within UAH, there exists a production and staging environment

• We would like to keep the staging environment
• We would like to remove the production environment

Local -> Staging (UAH) -> Test (MCP) -> Production (MCP)

DB Cleanup

Here is the current state of data in the existing environments

• Staging: dummy document data, dummy users
• Production (UAH): real GEDI ATBDs that can not be lost, both real and dummy users
• Production (MCP): Dummy document data, both real and dummy users

At the minimum, we need GEDI ATBDs withinUAH Production migrated to the Production MCP environment. Ideally:

• Staging stays the same
• Production (MCP) data moved to Test (MCP)
• Production (UAH) data moved to Production (MCP)

GEDI ATBD titles: Algorithm theoretical basis document for GEDI footprint aboveground biomass density Algorithm Theoretical Basis and Development of GEDI Level 2B Footprint Canopy Cover and Vertical Profile Metrics

This should be done prior to tearing down the UAH environment as described above.

[aboydnw]

Initial plan after discussing with Leo and Oliver.

1. Go through the UAH API to generate PDFs for the 2 following ATBDs (the front-end build appears to be broken): Algorithm theoretical basis document for GEDI footprint aboveground biomass density Algorithm Theoretical Basis and Development of GEDI Level 2B Footprint Canopy Cover and Vertical Profile Metrics
2. Destroy and re-deploy the MCP stack (includes running database setup + creating cognito groups)
3. Use the custom data migration scripts to copy data from UAH prod to the cleaned out MCP prod
4. Have Daniel re-deploy the frontend with the updated URL

We are punting on deploying a test stack in MCP. We will revisit later in the quarter.

[leothomas]

Done as part of release v2.4.0-beta

[deborahUAH]

@xhagrg before I close this ticket I would like to know the status of APT operation. What is on UAH? What is on MCP? is APT anywhere else (i.e. DevSeed)? I would think all of APT needs to be on MCP, right? there should be development, staging/testing, and production, correct? Please discuss with DevSeed and sort out. Record here what is the current architecture. Thanks!

[xhagrg]

As far as I know:

1. All of prod is in MCP.
2. dev and staging are in devseed's account (i think).
3. asking for an architecture diagram from devseed.