liquidmetal-dev / liquidmetal-dev/battery

Pool image/version rollout: rolling replacement of warm VMs

Open
#74 0 comments 0 reactions 0 assignees View on GitHub
enhancement priority/high
Dominant language
Go
Stars
1
Forks
0
Avg merge
2h 13m
Merged PRs (30d)
33

Description

When a pool's underlying flintlock image/kernel spec changes, add a rolling-replacement strategy that swaps out existing warm VMs for ones built from the new spec without dropping pool availability. Fits into the existing per-pool reconciler/replenishment strategy.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the existing per-pool reconciler and replenishment strategy mentioned in the issue, tracing how warm VMs are selected and created from the flintlock image/kernel spec. Define the rollout behavior so existing VMs are replaced with ones using the new spec while pool availability is maintained.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.