cirruslabs / cirruslabs/cirrus-cli
Support Distributing of large artifacts via BitTorrent
- Dominant language
- Go
- Stars
- 285
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
We should investigate an option of a feature to distribute large artifacts to persistent workers via BitTorrent. A use case is to distribute large VMs for the isolation feature (#198). Each VM can be up to 60Gb and distributing an update to dozens or hundreds of workers from a single server is just too slow.
Cirrus Cloud can act as tracker and the CLI will receive a download assignment on a poll.
TBD is how to provide a torrent file and how to upload a file for seeding... Just creating the issue to open a discussion.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests. Start by tracing the CLI polling flow and the Cirrus Cloud tracker role described in the issue, then clarify how torrent files are provided and how uploaded artifacts are seeded. Done should be a decided, bounded design for distributing large VM artifacts to persistent workers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cloud, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100