liquidmetal-dev / liquidmetal-dev/battery
Image pre-warming/caching across flintlock hosts
Open
Nobody has claimed this yet.
enhancement
priority/medium
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 33
Description
Pre-pull/cache VM images and kernels across flintlock hosts ahead of replenishment to reduce provisioning latency when the reconciler needs to boot new warm VMs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the reconciler and the code that provisions warm VMs and handles image or kernel availability on flintlock hosts. Define how pre-pulling and caching should run across hosts before replenishment, then verify that replenishment can use cached artifacts and reduces provisioning latency.
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
- Needs clarification
- Newbie friendliness
- 35/100