Actions
Feature #23191
closedcluster-activity workflow usability improvements
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Target version:
Story points:
-
Release:
Release relationship:
Auto
Description
source:tools/cluster-activity includes a workflow, but it's hard to use:
- The workflow is only included in the Arvados source
- It's not documented
- It depends on a Docker image that we don't publish
Improve this situation:
- Include a
dockerFileso the workflow can build itself - Document how to register and run the workflow
- Make sure that when you
pip installthe package you get the workflow somewhere appropriate.
Updated by Brett Smith 6 months ago
- Related to Bug #22216: cluster-activity workflow fails to pull Docker image added
Updated by Brett Smith 6 months ago
- Related to Bug #22590: arvados-user-activity and arvados-cluster-activity missing python package descriptions added
Updated by Brett Smith 6 months ago
- Release changed from 83 to 79
- Target version set to Development 2025-10-15
- Assigned To set to Brett Smith
- Description updated (diff)
Updated by Brett Smith 6 months ago
23191-cluster-activity-workflow @ 567b3b1cd9378901c62bc2fe40cba45b79545a1d - developer-run-tests: #4899
This branch makes the cluster activity workflow more usable.
- The workflow no longer depends on an unpublished Docker image.
- The workflow includes documentation for itself and parameters.
- Optional inputs are better handled in the underlying tool.
This branch improves both the workflow and the tool. You can test the workflow as-is if you provide Prometheus credentials. If you want to test without those credentials, run these commands from the checked-out branch:
$ build/build_docker_image.py --env=dev --tag=arvados/cluster-activity:latest arvados/cluster-activity $ arv-keepdocker arvados/cluster-activity
Then you'll be able to run the workflow with the improved input handling.
- 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.
- N/A
- Code is tested and passing, both automated and manual, what manual testing was done is described.
- In addition to above, tested the new workflow on my single-node development cluster.
- Tested code incorporates recent main branch changes.
- Yes
- New or changed UI/UX and has gotten feedback from stakeholders.
- N/A, no interface changes, just documenting the existing interface
- Documentation has been updated.
- Very much so
- Behaves appropriately at the intended scale (describe intended scale).
- No change in scale
- Considered backwards and forwards compatibility issues between client and server.
- N/A
- Follows our coding standards and GUI style guidelines.
- Yes
Updated by Brett Smith 5 months ago
- Related to deleted (Bug #22590: arvados-user-activity and arvados-cluster-activity missing python package descriptions)
Actions