Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] [GCP Cluster launcher] Use single SSH key for all tests #40677

Merged
merged 5 commits into from
Nov 13, 2023

Conversation

architkulkarni
Copy link
Contributor

@architkulkarni architkulkarni commented Oct 25, 2023

Why are these changes needed?

Previously a new key would be generated by the cluster launcher for each test run. This caused us to hit the limit for the number of SSH keys per project. This PR uses a single SSH key for all tests by storing a key in a GCS bucket and downloading it to each test cluster at startup.

Related issue number

Closes #40635

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@architkulkarni architkulkarni marked this pull request as ready for review October 31, 2023 16:57
@architkulkarni architkulkarni requested review from ericl and a team as code owners October 31, 2023 16:57
@architkulkarni
Copy link
Contributor Author

Screenshot 2023-10-31 at 9 58 04 AM GCP cluster launcher tests passed. (gcp-cluster-launcher-release-image is expected to fail on PR builds.)

@architkulkarni
Copy link
Contributor Author

@rickyyx Do you mind reviewing this as codeowner?

Copy link
Contributor

@rickyyx rickyyx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


via GIPHY

@rickyyx
Copy link
Contributor

rickyyx commented Nov 13, 2023

hmmm, we should add you or other folks as code owners for this.

@architkulkarni
Copy link
Contributor Author

@rickyyx yeah good point, I'm codeowner but I can't approve my own PR... We'll figure out a better solution (maybe @hongchaodeng we can add you as another codeowner for OSS cluster launcher?)

@architkulkarni
Copy link
Contributor Author

Failed tests unrelated, this PR only modifies the GCP cluster launcher tests

@architkulkarni architkulkarni merged commit dc945e0 into ray-project:master Nov 13, 2023
32 of 47 checks passed
ujjawal-khare pushed a commit to ujjawal-khare-27/ray that referenced this pull request Nov 29, 2023
…ject#40677)

Previously a new key would be generated by the cluster launcher for each test run. This caused us to hit the limit for the number of SSH keys per project. This PR uses a single SSH key for all tests by storing a key in a GCS bucket and downloading it to each test cluster at startup.

Related issue number
Closes ray-project#40635

---------

Signed-off-by: Archit Kulkarni <[email protected]>
Signed-off-by: Archit Kulkarni <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI] [Cluster launcher] GCP cluster launcher tests should all use the same SSH key
4 participants