Nomad Pack Community Registry

The ceph_rbd_csi pack deploys the Ceph RBD CSI plugin using two types of Nomad jobs:

1. Node plugin tasks: Run as a system job to ensure they run on all applicable clients.
2. Controller tasks: Run as a service job to manage the lifecycle of volumes.

This pack automates the deployment of the CSI driver components required to provide Ceph RBD storage to Nomad workloads.

The Ceph pack deploys a Ceph container in "demo" mode, where a single container runs all required services.

Warning: This pack is intended for demonstration purposes and is not suitable for production. If the allocation is rescheduled, all data written to Ceph will be lost. It is primarily used to provide a target for the ceph_rbd_csi pack.

The tempo pack deploys a single instance of the Grafana Tempo distributed tracing backend. It uses the grafana/tempo Docker image and registers a Consul Service named tempo.

Tempo is designed to be a high-scale, cost-efficient tracing backend that operates using object storage and integrates deeply with Grafana, Prometheus, and Loki. It supports standard tracing protocols including Jaeger, Zipkin, and OpenTelemetry.

This pack deploys the Prometheus Consul Exporter as a Nomad service job. It uses the Docker driver to run the exporter. By default, the task registers a Consul service and a health check. Once deployed, you can configure Prometheus to discover and scrape these instances using Consul service discovery (consul_sd_configs).

- job_name: "consul_exporter"
  metrics_path: "/metrics"
  consul_sd_configs:
    - server: "consul.example.com:8500"
      services:
        - "prometheus-consul-exporter"

The Vector pack deploys a single system job that runs Vector across all Nomad clients. It is designed to collect and forward observability data from three primary sources:

1. Docker logs: Collected via the Docker socket.
2. Host metrics: Collected using Vector's built-in collector (CPU, memory, disk, network).
3. Nomad metrics: Collected via the Nomad Prometheus client.

Data is forwarded to:

• Loki: For Docker logs (supports basic authentication).
• Prometheus: For host and Nomad metrics via remote write (supports basic authentication).

Currently, the pack only supports the docker driver.

The Backstage pack deploys a service job that runs Backstage alongside a PostgreSQL database within a single Nomad client. It uses the Docker driver for task execution.

Key Architecture Details:

• Service Communication: Handled natively by Nomad.
• Persistence: PostgreSQL state is persisted using Nomad Host Volumes.

The WordPress pack deploys a WordPress CMS instance within a single Nomad client using the Docker driver. It consists of three interconnected tasks:

1. WordPress: The open-source CMS.
2. MariaDB: The database used by WordPress.
3. phpMyAdmin: A web-based interface for MariaDB administration.

Key Architectural Features:

• Service Communication: Handled via Consul Connect using sidecar proxies.
• Persistence: MariaDB state is persisted using Nomad Host Volumes.
• Service Discovery: Consul service registration and health checks are enabled by default for WordPress and phpMyAdmin (MariaDB only has registration enabled).

This pack deploys a single system job that runs the AWS EFS CSI plugin in monolith mode (running both as nodes and controllers).

Prerequisites:

• Nomad hosts must have Docker privileged mode enabled.
• Nomad hosts must have access to AWS EFS via AWS IAM.

Key Features:

• Deploys the amazon/aws-efs-csi-driver:master Docker image by default.
• Uses the aws-efs CSI ID.