-
Notifications
You must be signed in to change notification settings - Fork 470
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
Support start and stop Azure instances #316
Conversation
d36e2f7
to
5fe06d1
Compare
5fe06d1
to
70f1855
Compare
Note: ready for review. The test failure is related to new azure-cli versions, will be fixed later |
b0a3e11
to
43a8764
Compare
Ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. @Michaelvll should know more about the versioning fixes.
@@ -197,10 +197,11 @@ def check_credentials(self) -> Tuple[bool, Optional[str]]: | |||
# This file is required because it will be synced to remote VMs for | |||
# `az` to access private storage buckets. | |||
# `az account show` does not guarantee this file exists. | |||
if not os.path.isfile(os.path.expanduser('~/.azure/accessTokens.json')): | |||
azure_token_cache_file = '~/.azure/msal_token_cache.json' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the difference between:
- ~/.azure/accessTokens.json
- ~/.azure/msal_token_cache.json (sounds like a cache)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
~/.azure/accessTokens.json
is the cache for older azure-cli, ~/.azure/msal_token_cache.json
is the cache for the new version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upgrading the azure-cli
sounds good to me. With this, I think we can upgrade the remote ray version safely without upgrading the local ray version.
* azure external node provider * allow stopping Azure * update token check
Update
azure-cli
to2.30.0
. Update smoke tests.Closes #148