- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 4 2022
The backup is in sync, everything is back to normal
Now let's restart the synchronization:
root@backup01:~# zfs destroy -r data/sync/dali/postgresql root@backup01:~# systemctl reset-failed syncoid-dali-postgresql.service root@backup01:~# systemctl restart syncoid-dali-postgresql.service
and the same for data/sync/dali/postgresql_wall
The disk needed to be detached and reattached in order to be resized.
It seems zfs didn't detect the pool after the reboot.
A reimport did the work:
root@backup01:~# zpool import data root@backup01:~# zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT data 255G 188G 66.9G - - 9% 73% 1.00x ONLINE -
(The pool is still correctly detected after a reboot)
The disk is sized at 200G, according to the azure portal, it can be resized to 256 without any additional cost.
Enter the size of the disk you would like to create. You will be charged the same rate for your provisioned disk, regardless of how much of the disk space is being used For example, a 200 GiB disk is provisioned on a 256 GiB disk, so you would be billed for the 256 GiB provisioned.
May 3 2022
- rebase
- test the prometheus exporter file creation
May 2 2022
Apr 21 2022
Good news, it looks like there is no more issues with the inter-node communication with rancher 2.6.4 and bullseye.
gg ;)
Apr 20 2022
Rebase
Thanks, we will look later how to have a better zpool initialization
There is no occurrences of this error in the logs and the consumers don't have any lag, so yes, I guess it is.
rebase
Apr 19 2022
Apr 15 2022
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.
Apr 14 2022
rebase
Apr 13 2022
Apr 12 2022
don't provision a public ip for rancher
rebase
Apr 11 2022
Apr 8 2022
Update the commit title
Rebase and adapt
Apr 7 2022
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
Apr 6 2022
Thanks olasd for the feedback.