FlyBackend supports mounting volume
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start with the FlyBackend implementation and the abandoned PR #22 to understand the existing volume-mounting approach. Check how Fly volume IDs, instance creation, autoscaling, and concurrent runner startup interact; done means a built-in solution supports the requested volume behavior without hardcoded project-specific values.
Written by the indexing model from the issue text.
Description
I'm using FLAME for my project to run ML workload running on Fly. To avoid download the 4GB model data every time starting a FLAME runner, a Fly volume needs to be attached to the instance.
Currently there is a PR https://github.com/phoenixframework/flame/pull/22 by @benbot, however, it seems abandoned for 3 months.
Token a brief look, the tricky part seems that:
- Fly volumes don't auto-scale when creating new instance,
- and the API requires the caller to explicit specify the volume id instead of just the name.
This might become trickier when multiple nodes in the cluster trying to start the runners at the startup time causing potential race condition.
I currently forked the FlyBackend and hardcoded the volume info to make things working in my project. But a proper built-in solution would be very nice.
- Dominant language
- Elixir
- Stars
- 1.2k
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from phoenixframework/flame
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
phoenixframework/flame#86 · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
phoenixframework/flame#84 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
phoenixframework/flame#75 · 2 comments ·
-
Clean up code_sync tmp files on terminator shutdownMay be free again @chrismccord claimed this 674 days ago, and no pull request is open. Open
phoenixframework/flame#70 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
phoenixframework/flame#66 · 1 comment ·
All issues in phoenixframework/flame
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
semaphoreio/semaphore#1305 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QuinnWilton/argus#5 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
carverauto/serviceradar#5009 ·
Maintainers usually reply within 1 day