- Feb 27, 2025
-
-
- Feb 26, 2025
-
-
Nicolas Dandrimont authored
This reverts commit b3135c54.
-
Nicolas Dandrimont authored
-
- Feb 25, 2025
-
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
- Feb 24, 2025
-
-
- Feb 20, 2025
-
-
Vincent Sellier authored
Related to swh/infra/sysadm-environment#5510
-
Vincent Sellier authored
Related to swh/infra/sysadm-environment#5510
-
Vincent Sellier authored
-
Refs. swh/devel/swh-web!1389
-
-
-
-
- Feb 19, 2025
-
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
Somehow installing the db into the cluster-components fails the initialization of the db model by the svix-server. So install it in the swh namespace like the other backends. Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
- Feb 18, 2025
-
-
Antoine R. Dumont authored
Be it production or staging. The postgresql and redis backends are deployed independently from the svix template. Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
This enables svix on the next-version environment, it: - creates a new postgresql backend instance (with cnpg template) - creates a new redis backend instance (with redis template) - ties this all in a new svix-next-version svix server instance. Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
This is needed to deploy an instance in the next-version environment. Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5514
-
Antoine R. Dumont authored
The current cluster is yellow because it has 1 replica too many. Refs. swh/infra/sysadm-environment#5514
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5514
-
Antoine R. Dumont authored
It defaults to 200 [1] [1] https://gitlab.softwareheritage.org/swh/devel/swh-journal/-/blob/master/swh/journal/client.py#L155 Refs. swh/infra/sysadm-environment#5514
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5514
-
- Feb 17, 2025
-
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
-
Antoine R. Dumont authored
So it can either work from: - the tuple (--username, --password, --server) - a swh configuration file with celery.task_broker key entry (--config-file) - an amqp connection string (--amqp-url) Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-
Vincent Sellier authored
Related to swh/infra/sysadm-environment#5571
-
- Feb 14, 2025
-
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5547
-