Set PVC names in Ray ClusterConfig
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kubernetes, python
- Domain
- infrastructure
Research direction
Start by locating the ClusterConfig definition and the rendering path for the Ray object, then compare it with templates/base-template.yaml from the referenced v0.19.0 SDK. Done means accepting persistent_volume_claims: List[str] in ClusterConfig and passing the supplied PVC names through to the generated Ray configuration without requiring a customized template.
Written by the indexing model from the issue text.
Description
Name of Feature or Improvement
I would like to be able to pass PVC names to a ClusterConfig.
Description of Problem the Feature Should Solve
When I create Ray clusters through the SDK, I couldn't find a way to add PVC name(s) to be added to the Ray object. I would like to be able to pass PVC names to a ClusterConfig instead of having to add that to a customized base template.
I am not using S3 endpoints, therefore that is not useful to me.
Describe the Solution You Would Like to See
Add persistent_volume_claims: List[str] to the ClusterConfig definition
Describe Alternatives You Have Considered
Copy https://github.com/project-codeflare/codeflare-sdk/blob/v0.19.0/src/codeflare_sdk/templates/base-template.yaml, edit and pass it through the template parameter.
- Dominant language
- Python
- Stars
- 35
- Forks
- 66
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 project-codeflare/codeflare-sdk
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
project-codeflare/codeflare-sdk#1195 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
project-codeflare/codeflare-sdk#1190 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
project-codeflare/codeflare-sdk#813 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
project-codeflare/codeflare-sdk#425 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
project-codeflare/codeflare-sdk#422 · 1 comment ·
Maintainers usually reply within 1 day
All issues in project-codeflare/codeflare-sdk
Similar issues
-
good first issue test
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ANCORATE/EncryptHome#8 ·
-
PluginProvider.storeInstance races and clobbers the dedup cache for concurrent loadsPossibly taken @Wilson0511 claimed this today. Openneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 2 days
-
Bug: failed Together chat calls do not record operation duration or error.typePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
community documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100