Have responsibilities to deploy Nasqueron application using Docker.
This group is mainly intended to give permissions to automated agents in the build process.
Have responsibilities to deploy Nasqueron application using Docker.
This group is mainly intended to give permissions to automated agents in the build process.
Without performance benchmark, the expected gain is not obvious.
web-001 on the same hypervisor has correct IPv6 support, we can do the same for Hervil with the /56 trick and the hello trick:
Not sure of the current benefit to use TC2.
Salt SELinux module issue
SELinux context was the default for anything created under /var, which we didn't allow and aren't interested to allow for nginx.
Mumble isn't currently in scope.
If we want to fix that at docker-py level, we can also apply this patch: https://github.com/docker/docker-py/pull/3257/files
Per discussion with @fauve.
Deployed at https://grafana.nasqueron.org/
With a transformation, we can multiply the field by 10 to solve that issue: https://grafana.nasqueron.org/d/fdsy3oogbchs0f/graphite-quux-sandbox?orgId=1&tab=transform&from=1722018733917&to=1722022333917
The graphite Docker image provides both pieces of software.
DNS: grafana. CNAME www-dev.nasqueron.org
Deployment can be using sqlite3 as long as it's still performant
as we want our monitoring tools to be resiliant.
This task has been created in 2016 to publish metrics from PCP (Performance Co-Pilot) on RHEL-like servers, especially our Docker engines.