rebase

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.

rebase

Thanks

don't provision a public ip for rancher

rebase

Update the commit title

Rebase and adapt

reduce the history to 90 days

rebase

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

Thanks olasd for the feedback.

Fix a typo on the title

LTGM for what it's worth ;)

The site is deployed and available at https://azure-billing.internal.admin.swh.network/

add the tfstate update after the creation of the server

Thanks olasd for restarting the service following this documentation: https://docs.gunicorn.org/en/stable/signals.html#upgrading-to-a-new-binary-on-the-fly

First, replace the old binary with a new one, then send a USR2 signal to the current master process. It executes a new binary whose PID file is postfixed with .2 (e.g. /var/run/gunicorn.pid.2), which in turn starts a new master process and new worker processes:
At this point, two instances of Gunicorn are running, handling the incoming requests together. To phase the old instance out, you have to send a WINCH signal to the old master process, and its worker processes will start to gracefully shut down.

Sorry the description was not completely clear
The durations metrics are still updated, but not the operations count ones
In 2 metrics at 10 minutes of interval:

vsellier@saam ~ % ls -al /tmp/m[12]              
-rw-r--r-- 1 vsellier vsellier 176850 Mar 30 07:25 /tmp/m1
-rw-r--r-- 1 vsellier vsellier 176846 Mar 30 07:34 /tmp/m2

the scripts finally land in the puppet repository (D7456)