Skip to content

Perform v0.17.0 Data Migration and Release #532

@jayfo

Description

@jayfo

Issue for tracking data migration and release of v0.17.0.

Steps to prepare for migration and release:

  • Export pre-flight archives for:

    • dev
    • demo
    • multicare
    • scca
  • Validate pre-flight archive to confirm pre-migration failure for:

    • dev: Ignoring Anant account. No migration needed, none expected.
    • demo: No migration needed, none expected.
    • multicare: No migration needed, none expected.
    • scca: No migration needed, none expected.
  • Develop migration scripts:

    • N/A
  • Create release branch based on develop:

    • release/v0.17.0
  • Ensure scope-aws-infrastructure Pipfile is using current release.

    • release/v0.17.0
  • If migration required, validate migration script with migrated versions of pre-flight archives:

    • dev: No migration needed.
    • demo: No migration needed.
    • multicare: No migration needed.
    • scca: No migration needed.
  • Build images, requires updating version in 6 places:

    • docker/server_flask/codebuild_env.sh
    • docker/web_patient/codebuild_env.sh
    • docker/web_registry/codebuild_env.sh
    • tasks/codebuild/server_flask.py
    • tasks/codebuild/web_patient.py
    • tasks/codebuild/web_registry.py

Steps to execute migration and release:

  • Freeze the database by stopping the associated server-flask, web-patient, web-registry services. This requires manually stoping each release with a helm uninstall command on the server (i.e., because the --skip-crds default in our Helmfile conflicts with installed).

    • dev
    • demo
    • multicare
    • fredhutch and scca
  • Export final pre-migration archive:

    • dev
    • demo
    • multicare
    • scca
  • If migration not required, validate final pre-migration archive:

    • dev
    • demo
    • multicare
    • scca
  • If migration required, apply and validate the migration.

    • dev
    • demo
    • multicare
    • scca
  • If migration required, reset the database.

    • dev
    • demo
    • multicare
    • scca
  • If migration required, restore the migrated archive.

    • dev
    • demo
    • multicare
    • scca
  • Update Helmfile imageTag values for associated server-flask, web-patient, web-registry services.

    • dev
    • demo
    • multicare
    • fredhutch and scca
  • Apply Helmfile to deploy release based on migrated data.

    • dev
    • demo
    • multicare
    • fredhutch and scca

Upload archives to Microsoft Teams.

  • dev
  • demo
  • multicare
  • scca

Document release deployments

  • Update v0.16.2 release data
  • Update v0.17.0 release data

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions