Add metabase stack ⚠️ (manual action required)

[YuryHrytsuk]

What do these changes do?

Details:

• metabase stores its data in (already running) postgres database
• backups included
• highly available (multiple replicas + persistent storage)
• docker and traefik healthcheck are configured
• prometheus scraping is configure (metabase-specific metrics)

Extra todo:

• db backups (done manually)
  • later will be done in e2e tests Metabase: add database backup test #1094

Manual action ⚠️

remove existing readonly user (if any)

1. Revoke connect to database REVOKE CONNECT ON DATABASE <mydb> FROM <user>;
2. Follow https://github.com/ITISFoundation/osparc-simcore/blob/22374df75beb805c1b57873a1b74b1f89557709c/services/postgres/scripts/remove-readonly-user.sql.template

create read only (non-login) user
Follow instructions in ITISFoundation/osparc-simcore#7997

create read only user
Follow instructions in ITISFoundation/osparc-simcore#7997

create metabase user and database
Follow instructions in ITISFoundation/osparc-simcore#7997

restart pgbackup (do as last step)
pg_backup needs to be restarted. This will triger pgenv.sh regeneration and new database (for metabase) will be added and thus backed up

Create metabase admin user

1. manually go to metabase url and create a user (use the same devops email)
2. save admin credentials

Source: https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/merge_requests/1469/diffs

How to deploy

1. Create metabase user and database user via scripts from ♻️ Update postgres configuration ⚠️ DEVOPS osparc-simcore#7997
2. Run Release CI

Related issue/s

• Closes Deploy metabase and provide access to selected app-team members #1061

Related PR/s

• ♻️ Update postgres configuration ⚠️ DEVOPS osparc-simcore#7997
• configuration https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/merge_requests/1449
• Sql scripts to be migrated to Create mechanism to create/update or delete new users in database #827 (if implemented)

Checklist

• I tested and it works

CI:

• The Stack has been included in CI Workflow

New Service:

• Service has resource limits and reservations
• Service has placement constraints or is global
• Service is restartable
• Service restart is zero-downtime
• Service has >1 replicas in PROD
• Service has docker heathlcheck enabled
• Service is monitored (via prometheus and grafana) --> no special grafana dashboard
• Service is not bound to one specific node (e.g. via files or volumes)
• Relevant OPS E2E Test are added
  • Test backups (todo later Metabase: add database backup test #1094)

Exposed via traefik:

• Service's Public URL is included in maintenance mode --> not relevant (ops services are not handled by maintenance)
• Service's Public URL is included in testing mode --> not relevant
• Service's has Traefik (Service Loadbalancer) Healthcheck enabled
• Credentials page is updated
• Url added to e2e test services (e2e test checking that URL can be accessed)

[pcrespov]

thx!