Backup done:

well, no, computer says no ¯\_(ツ)_/¯

fwiw, we're received notifications that the upstream repository have been delivered with some fixes.
So i've pulled the upstream branch and rebase the swh branch on it.

"Full" (with the overall sysadm repositories) run [1].

Another "private" (for the test) repository to try and migrate [1], it should be private but it's not [2]:

Added 2 more repositories [1] to migrate and triggered it [2] [3]:

It seems to have finished badly [1].
But that may only be because it's configured to run in debug mode.
Latest run logs for later [2]

Migration is now ongoing without failing thus far.
Configured to only import puppet-environment for now [1] (to fix papercuts).
But that's still migrating the rest (users, issues, etc...).

Summary sent to Frank Duncan and Karl Fogel.

Clean up gitlab instance

Gist of the actions are currently:

• Mirror the forgerie repository to add some docker commands to allow sandboxed execution (see diffs ^)
• Adaptations in the forgerie code source to allow migration runs with our current gitlab/phabricator instances (see diffs ^)
• Current runs are working a bit but do not succeed entirely

A restoration of the azure instance on our infra was successfully performed [1].
Everything is well imported: users, repositories, issues, ...
The usage of a quick and dirty longhorn storage seems to make the instance slower than azure but the performance was not the goal of this POC.

Status update:

• The global installation process is defined
  • The static ip is configured during the terraform deployment
• The ability to monitor the cluster and the gitlab is verified
  • Prometheus url with the kubernetes stats (for federation) : http://192.168.200.15:9090
  • Temporary grafana to have an idea of the possible dashboards: http://192.168.200.15:3000
  • Gitlab exported stats (exporter to add on the pergamon's prometheus):
    • Readiness probe: https://gitlab-staging.swh.network/-/readiness?token=<token>
    • Liveness probe: https://gitlab-staging.swh.network/-/liveness?token=<token>
    • Prometheus exporter: https://gitlab-staging.swh.network/-/metrics?token=<token>

The token can be found on the dedicated gitlab page: https://gitlab-staging.swh.network/admin/health_check

• outbound emails: Solved by creating a gandi's inbox and configuring the deployment to use it

The test instance can be reached at https://gitlab-staging.swh.network

The following installation methods were tested:

1. debian packages
2. docker image
3. helm charts
4. gitlab operator