[Feature] Integration test case with Data Science Pipeline, CodeFlare and KubeRay
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kubernetes, python, scikit-learn
Research direction
Start with the scikit-learn document-clustering example and map the six listed pipeline stages to the DSP YAML, test image, and CodeFlare image described in the issue. Done means a public-data, non-proprietary run completes in under 20 minutes within the stated Ray resource limits and reports both actor evaluations before shutdown.
Written by the indexing model from the issue text.
Description
Name of Feature or Improvement
Create an integration test case to validate DSP, CodeFlare and KubeRay implementation.
Describe the Solution You Would Like to See
Test environment assumptions:
- Data Science Pipeline v1.
- Ray cluster shall consist of no more than 2 worker pods, with 2 CPU cores and less than 6 GB available for each pod.
- An integration test execution time shall be less than 20 mins in total.
- S3 storage may be available, if needed.
- Free of proprietary intellectual property.
- Public data only.
Proposed test case: Clustering text documents using k-means on scikit-learn education page.
https://scikit-learn.org/stable/auto_examples/text/plot_document_clustering.html
Data Science Pipeline stages:
- Downloading test data (https://scikit-learn.org/stable/auto_examples/text/plot_document_clustering.html#loading-text-data)
- Launch Ray cluster with two worker pods.
- Ray driver launches two Ray actors, deployed to a pod each. The first actor runs TfidfVectorizer, followed by Kmeans clustering and evaluation. The second actor runs HashingVectorizer, followed by Kmeans clustering and evaluation.
- Ray driver collects evaluation results from the two actors. Then it reports the summaries.
- Ray cluster is stopped and shutdown.
- Pipeline run is completed.
Expected test assets:
- DSP pipeline yaml to deploy and kick off test runs.
- Test image with Ray and document clustering code.
- CodeFlare image to deploy the test image.
- Preconfigured credentials and configmaps in the test environment.
- 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 3/5 1-2 days Newbie friendliness 38/100
project-codeflare/codeflare-sdk#774 ·
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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#147104 ·
Maintainers usually reply within 1 day
-
premises-missing
Difficulty 1/5 Under an hour Newbie friendliness 88/100
WingedGuardian/GENesis-AGI#3801 ·
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Document new required `shared-org-key` input for `obs-aw-dependency-review`Possibly taken @github-actions claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
bot-triaged module: inductor oncall: pt2 topic: fuzzer triaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 4 days