← Back to issue list

`spread.yaml` templates: consider LXD VMs over or in addition to multipass

View original Github issue

Metadata

Project
charmcraft
Number
#1923
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

Exploratory request to use LXD VMs in generated Spread templates instead of Multipass; the targeted experimental templates were later removed, and current templates use the Craft backend.

Suggested action: close stale

Reason: Commit 73ed7267 (#2118) explicitly removed the experimental Spread init templates targeted by this request, while the current generated templates use a Craft backend rather than Multipass. With no comments, acceptance criteria, or follow-up for 413 days, this legacy exploration is obsolete rather than an actionable defect.

Evaluated by: mr-cal-bot

Impact: 22 Quick Win: 3 Complexity: 58 Confidence: 88 Actionability: 28

Issue body

### What needs to get done For templates with `spread.yaml`, consider whether/how to use lxd vms . ### Why it needs to get done Good point brought up by @jnsgruk here: https://github.com/jnsgruk/zinc-k8s-operator/pull/267#discussion_r1774983269

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 22
Quick Win: 3
Complexity: 58
Confidence: 88
Actionability: 28
close stale Exploratory request to use LXD VMs in generated Spread templates instead of Multipass; the targeted experimental templates were later removed, and current templates use the Craft backend.
~deepseek/deepseek-pro-latest
Impact: 30
Quick Win: 3
Complexity: 50
Confidence: 55
Actionability: 20
close resolved Maintainer task to evaluate using LXD VMs instead of or alongside multipass in charm templates' spread.yaml test configs. No comments or labels; likely superseded by removal of experimental spread init templates.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 11
Complexity: 40
Confidence: 70
Actionability: 60
needs triage Consider adding LXD VM support to spread.yaml templates as an alternative or addition to the existing multipass backend
qwen/qwen3.8-27b
Impact: 40
Quick Win: 18
Staleness: 72
Complexity: 55
Confidence: 65
Support Request: 10
needs triage Feature request to consider using LXD VMs in charmcraft's spread.yaml templates (test-machine/test-kubernetes) instead of or in addition to multipass. No maintainer response or labels; last activity 381 days ago.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 45
Confidence: 75
Support Request: 5
needs triage Unlabelled feature request to evaluate LXD VMs as an alternative or addition to multipass for spread.yaml templates. Currently inactive with no maintainer comments or labels after over 18 months.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 20
Confidence: 80
Support Request: 0
close stale Proposal to evaluate LXD VMs for spread.yaml test templates instead of Multipass. Open for nearly two years with zero comments, labels, or maintainer engagement.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 20
Confidence: 80
Support Request: 10
needs triage Proposes evaluating LXD VMs as a replacement or addition to Multipass for spread.yaml test templates. Open with no maintainer comments, labels, or assignee after nearly two years.

Update history

No update history recorded yet.

Related work

  • Superseded By: canonical/charmcraft#2118 (confidence 96%)

    Commit 73ed7267 removed the experimental Spread init templates targeted by the issue.

  • Superseded By: canonical/charmcraft#2385 (confidence 80%)

    The custom test command was replaced by the upstream implementation; current templates use the Craft backend.

Related issues

No related issues found above the similarity threshold.