This file directory structure can be used for 4th year projects
(user-projects/(third/fourth)-year-project)
I can't validate this, but checkout this branch on one of the hosts and
run `nomad job validate <path>` to ensure the config is okay, followed
by `nomad job plan <path>` to plan it. Run the job at that point using
the check-id. Once you're happy that it runs, return to the master
branch and merge this PR.
nova@redbrick.dcu.ie requested this to be deployed.
A DNS entry will need to be made before planning to ensure that the cert
can be generated by traefik.
Add a local user and let them tunnel a port and connect to localhost
ssh -L 25565:10.10.0.4:<exposed port> <user>@glados.redbrick.dcu.ie -p
80
Then in the minecraft server settings on the client, type localhost
The change adds the Prometheus job. I had to go with certain assumptions
regarding the host constraint, as well as lack of volumes, but I hope
this serves as the base for running the monitoring stack on Nomad
itself.
The Prometheus instance is on purpose left unexposed, so that we can use
Grafana and additional authentication in that layer later.
