AbsaOSS / AbsaOSS/enceladus

Migration questions

Abierto
#1,875 0 comentarios 0 reacciones 0 asignados Ver en GitHub
cloud Menas priority: high question
Lenguaje dominante
Scala
Estrellas
33
Forks
16
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

## Background
As part of moving Enceladus to cloud, we need to get the existing configuration (dataset definitions) data to AWS.

## Question

#### What data can be exposed to cloud
Some data for regulatory reason cannot be in cloud. Does it include the Menas data?
(_Sasa_)

#### Which datasets to migrate
Get and keep updated a list of datasets to be migrated

#### What transformations
Analyze and prepare what transformation of the data need to be done during migration (e.g. path change)

#### How the migration will be done
Will the migration be a one of process or repeated or migration in phases?

#### Synchronization
Figure out of synchronization will be required or expected. E.g. not full migration but update on missing and changed datasets.
Empathize that two way sync would be **really bad*** (complex, fragile, maybe needing constant attention, cost over benefits,...)
(_Danil_, _rest of the team_)

#### When to do
When the migration can be expected to happen and or start, both for UAT and production environment

#### Who will maintain the migrated DBs and Menas Env
With the data migrated who will govern the infrastructure these data are on. Ensure proper resilience and data safety are in place.

#### Migrate the whole history
Archiving old data, perhaps (hopefully) before migration

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.