The zfs pool and dataset are configured:

• pool configuration

## nvme drives pool
#zpool create data mirror nvme-eui.36315030525005540025384500000003 nvme-eui.36315030525005800025384500000003 mirror nvme-eui.36315030525005620025384500000003 nvme-eui.36315030525005890025384500000003

I forgot to mention there is a gift from dell on the server: an additional 600Go 10rpm disk

The server is installed. It remains few task to perform manually:

• configure the zfs datasets (will configure 2 mirror pool for ~12To available, tell me if it's not what it's expected)
• build few missing packages for bullseye (relative to the monitoring: prometheus-rabbitmq-exporter, prometheus-statsd-exporter, journalbeat)
• configure a rabbitmq admin user

yes pgbouncer will be used and it's configured by default to 2000 // connections
I don't know the kind of load the provenance client will generate but the default 100 connections allowed by postgres will be probably too short and needed to be increased too

As see with @aeviso , we will install the following components on the server (the os will be debian11)

• rabbitmq
• postgresql:13
  • a default swh-storage database will be managed by puppet
  • 1000 parallel connections allowed
  • shared_buffers 50go
• docker

It looks ok for the puppet code

Interesting documentations on how to manage jobs:

• the different job pattenrs: https://kubernetes.io/docs/concepts/workloads/controllers/job/#job-patterns
• Using controllers to manage the workload: https://kubernetes.io/docs/concepts/architecture/controller/

• Remove useless ending '/'
• define VPN / private meanings

RabbitMq GUI -> RabbitMQ