[rfc] Support ray[aws,gcp,azure] as an install target

[richardliaw]

Describe your feature request

Currently, there's no automated way of obtaining cloud-specific autoscaler dependencies. users need to go to the docs (or risk an upgrade) when the code changes.

It'd be great if a user could just use pip install ray[aws] to obtain the right dependencies.

In practice, users would probably do:

pip install ray[aws,tune]

Other alternatives

pip install ray[cloud]
pip install ray[autoscaler
Both of these will install all dependencies for each cloud. But this is probably unpreferable because most users will only install 1 cloud at a time.

cc @ericl @edoakes @rkooo567 @pcmoritz

[richardliaw]

I'd be open to better suggestions for the name/targets too.

[pcmoritz]

This proposal sounds good to me, were there any alternatives you considered? One possibility is ray[autoscaler] or ray[clusterlauncher] with all of them, but it seems less preferable needing to install everything at once (as a pro, it makes it a bit clearer which user facing feature this enables).

[richardliaw]

Done, I left a comment about other options.

[vnlitvinov]

as a pro, it makes it a bit clearer which user facing feature this enables

If that is possible, targets could be named cloud+aws, cloud+gcp, etc.
I cannot check it right now because for some reason docs on pip and wheel are giving me "server error" right now :(

[pcmoritz]

as a pro, it makes it a bit clearer which user facing feature this enables

If that is possible, targets could be named cloud+aws, cloud+gcp, etc.
I cannot check it right now because for some reason docs on pip and wheel are giving me "server error" right now :(

In that case I don't think adding the cloud+ prefix adds a lot of value here, most people who are thinking of using them probably know that these are clouds :) If it were more specific like autoscaler+aws or clusterlauncher+aws that's different but then this is getting really long. Let's go with aws etc :)

[stale]

Hi, I'm a bot from the Ray team :)

To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.

If there is no further activity in the 14 days, the issue will be closed!

• If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
• If you'd like to get more attention to the issue, please tag one of Ray's contributors.

You can always ask for help on our discussion forum or Ray's public slack channel.

[vnlitvinov]

I think it's still relevant, is it not @richardliaw ?

[stale]

Hi, I'm a bot from the Ray team :)

To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.

If there is no further activity in the 14 days, the issue will be closed!

• If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
• If you'd like to get more attention to the issue, please tag one of Ray's contributors.

You can always ask for help on our discussion forum or Ray's public slack channel.

[vnlitvinov]

shoo bot