Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion docs/misc/firewall.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,6 @@ Pre-configured NodePorts for [DeepOps default service specs](/services) include:
- `tcp/30500`: Prometheus
- `tcp/30400`: AlertManager
- `tcp/30200`: Grafana
- `tcp/30700`: Kibana
- `tcp/30000`: Apt mirror

If a service is not listed here, it will use a random port from the range.
Expand Down
2 changes: 1 addition & 1 deletion docs/misc/syslog.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Centralized logging with syslog

Both the Slurm and Kubernetes cluster playbooks include a minimal implementation of centralized cluster logging using rsyslog.

Rsyslog was selected for the minimal cluster logging implementation in order to provide a light-weight solution using software already installed on the nodes. This ensures that logs are recorded in one place, making it easier to debug node-specific issues even in the case where the nodes are down or non-responsive. However, for a more full-featured logging solution with search and visualization capabilities, we recommend deploying the [ELK stack](../k8s-cluster/logging.md) or other log solution.
Rsyslog was selected for the minimal cluster logging implementation in order to provide a light-weight solution using software already installed on the nodes. This ensures that logs are recorded in one place, making it easier to debug node-specific issues even in the case where the nodes are down or non-responsive. However, for a more full-featured logging solution with search and visualization capabilities, consider a site-managed log stack; for Kubernetes clusters, see the Helm-based procedure in [logging](../k8s-cluster/logging.md).

In the syslog-based implementation, the first cluster management node is selected as a syslog server and listens on `rsyslog_client_tcp_port` for connections. The remaining nodes in the cluster then forward their logs to the selected syslog server. Log files for remote nodes are stored on the syslog server in node-specific files under `/var/log/deepops-hosts`.

Expand Down
86 changes: 0 additions & 86 deletions playbooks/slurm-cluster/logging.yml

This file was deleted.

12 changes: 0 additions & 12 deletions playbooks/slurm-cluster/templates/filebeat.conf

This file was deleted.

7 changes: 7 additions & 0 deletions roles/requirements.yml
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,10 @@ roles:
- src: nvidia.enroot
version: "v0.5.0"

- src: https://github.com/mrlesmithjr/ansible-maas.git
name: ansible-maas
version: '178a999c9bfc979ef32c42f4f59c034664df10d0'

- src: geerlingguy.filebeat
version: "3.5.0"

Expand All @@ -48,6 +52,9 @@ roles:
- src: robertdebock.kibana
version: "1.2.6"

- src: https://github.com/DeepOps/ansible-role-chrony
name: DeepOps.chrony
version: 'c9022153036dfdde4e2b313aecde4a46cd6f6687'

- src: https://github.com/OSC/ood-ansible.git
version: 'v3.0.3'
Expand Down
Loading