Feature #23329: Add arvados_alloy role to Ansible installer - Arvados

Actions

Copy link

Feature #23329

closed

Add arvados_alloy role to Ansible installer

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

Status:

Resolved

Priority:

Normal

Assigned To:

Stephen Smith

Category:

Deployment

Target version:

Development 2025-12-10

Story points:

Release:

Arvados 3.2.1

Release relationship:

Auto

Description

This shares some code with arvados_loki so we need to do a little reorganization for code sharing:

Add a distro_grafana role. Its responsibility is to set up the shared resources for the Grafana apt repository. It should take the tasks from arvados_loki that set up the deb822_repository and package pins. arvados_loki should now have a meta dependency on the distro_grafana role.
In the pin file in distro_grafana, add a pin for the alloy package to version 1.*.
Add an arvados_alloy role that follows the pattern of arvados_loki: it depends on distro_grafana. It's configured with a path arvados_alloy_config_file that it installs to /etc/alloy/config.alloy, installs the alloy package, and enables and re/starts the alloy systemd_service.

Subtasks 1 (0 open — 1 closed)

Related issues 1 (1 open — 0 closed)

Actions

Copy link

Updated by Brett Smith 4 months ago

Description updated (diff)

Actions

Copy link

Updated by Brett Smith 4 months ago

Target version set to Development 2025-12-10
Category set to Deployment

Actions

Copy link

Updated by Brett Smith 4 months ago

Related to Idea #18337: Easier install using Ansible added

Actions

Copy link

Updated by Brett Smith 4 months ago

Assigned To set to Stephen Smith

Actions

Copy link

Updated by Brett Smith 4 months ago

Subtask #23337 added

Actions

Copy link

Updated by Stephen Smith 4 months ago

Status changed from New to In Progress

Actions

Copy link

Updated by Stephen Smith 4 months ago

Changes at arvados|a51b2e9f5207a7f84d84c37fce14eb8bc12e4653 branch 23329-ansible-alloy

All agreed upon points are implemented / addressed. Describe changes from pre-implementation design.
- Yes
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.
- Tested running the install playbook with an alloy config file, verified correct version of alloy installed, config copied, and service running
The tested code incorporates recent main branch changes.
- Based off of main from 2 days ago
New or changed UI/UX has gotten feedback from stakeholders.
- n/a
Documentation has been updated.
- Added example to inventory
Behaves appropriately at the intended scale (describe intended scale).
- no change in scale
Considered backwards and forwards compatibility issues between client and server.
- The loki role used arvados-loki.pref for the pin, but now we have both pins in arvados-grafana.pref - any system that ran the old play might have redundant pref files
Follows our coding standards and GUI style guidelines.
- n/a

Actions

Copy link

Updated by Lucas Di Pentima 4 months ago

The 'apt update' handler is declared in the 'distro_apt' role, so I think the 'distro_grafana' role should depend on it instead of having that dependency on the 'arvados_loki' & 'arvados_alloy' roles.

The rest LGTM, thanks

Actions

Copy link