Project

General

Profile

Actions

Feature #23357

closed

Add arvados_prometheus role to Ansible installer

Added by Brett Smith 3 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Target version:
Story points:
-
Release relationship:
Auto

Description

Follow the same pattern as the Loki and Alloy roles we currently have:

  • In our distro_grafana role, add a pin for Prometheus version 2.*
  • Add an arvados_promtheus role that depends on distro_grafana. It:
    • Installs the prometheus package
    • Installs the configured arvados_prometheus_config_file to the right place
    • Enables and re/starts the service
  • Add a play to install-arvados-cluster.yml so hosts in the arvados_prometheus group run the arvados_prometheus role.

Subtasks 1 (0 open1 closed)

Task #23366: Review 23357-ansible-prometheusResolvedStephen Smith12/15/2025Actions
Actions #1

Updated by Brett Smith 3 months ago

  • Assigned To changed from Lucas Di Pentima to Stephen Smith
Actions #2

Updated by Brett Smith 3 months ago

  • Subtask #23366 added
Actions #3

Updated by Stephen Smith 3 months ago

  • Status changed from New to In Progress
Actions #4

Updated by Stephen Smith 3 months ago

Changes at arvados|c37cde1098440bb6c6610f32d4edcb3ea3806d17 branch 23357-ansible-prometheus
Tests test-provision-ansible: #19

  • All agreed upon points are implemented / addressed. Describe changes from pre-implementation design.
    • Added arvados_prometheus role that depends on distro_apt
    • Task installs, copies config with appropriate permissions, and starts/restarts when config updated
    • Added to playbook and example inventory
  • Anything not implemented (discovered or discussed during work) has a follow-up story.
    • none
  • Code is tested and passing, both automated and manual, what manual testing was done is described.
    • Checked that the playbook installs prometheus, copies the file, and enables the service
  • The tested code incorporates recent main branch changes.
    • yes
  • New or changed UI/UX has gotten feedback from stakeholders.
    • n/a
  • Documentation has been updated.
    • none
  • Behaves appropriately at the intended scale (describe intended scale).
    • no change
  • Considered backwards and forwards compatibility issues between client and server.
    • none
  • Follows our coding standards and GUI style guidelines.
    • n/a
Actions #5

Updated by Lucas Di Pentima 3 months ago

This LGTM, thank you!

Actions #6

Updated by Stephen Smith 3 months ago

  • Status changed from In Progress to Resolved
Actions #7

Updated by Brett Smith about 2 months ago

  • Release set to 84
Actions

Also available in: Atom PDF