-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Tests and docs for ability to specify subdirectory to download for LocalizePath #6308
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
Changes from all commits
a91ec15
8f9bd75
59d377f
adb69e9
e68e568
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -169,6 +169,45 @@ for ENV_VAR in "shared_key"; do | |
wait $SERVER_PID | ||
done | ||
|
||
# Test localization to a specified location | ||
export TRITON_AZURE_MOUNT_DIRECTORY=`pwd`/azure_localization_test | ||
|
||
if [ -d "$TRITON_AZURE_MOUNT_DIRECTORY" ]; then | ||
rm -rf $TRITON_AZURE_MOUNT_DIRECTORY | ||
fi | ||
|
||
mkdir -p $TRITON_AZURE_MOUNT_DIRECTORY | ||
|
||
SERVER_LOG=$SERVER_LOG_BASE.custom_localization.log | ||
SERVER_ARGS="--model-repository=$MODEL_REPO --exit-timeout-secs=120" | ||
|
||
run_server | ||
if [ "$SERVER_PID" == "0" ]; then | ||
echo -e "\n***\n*** Failed to start $SERVER\n***" | ||
cat $SERVER_LOG | ||
exit 1 | ||
fi | ||
|
||
if [ -z "$(ls -A $TRITON_AZURE_MOUNT_DIRECTORY)" ]; then | ||
echo -e "\n***\n*** Test localization to a specified location failed. \n***" | ||
echo -e "\n***\n*** Specified mount folder $TRITON_AZURE_MOUNT_DIRECTORY is empty \n***" | ||
ls -A $TRITON_AZURE_MOUNT_DIRECTORY | ||
exit 1 | ||
fi | ||
|
||
kill $SERVER_PID | ||
wait $SERVER_PID | ||
|
||
if [ -d "$TRITON_AZURE_MOUNT_DIRECTORY" ] && [ ! -z "$(ls -A $TRITON_AZURE_MOUNT_DIRECTORY)" ]; then | ||
echo -e "\n***\n*** Test localization to a specified location failed. \n***" | ||
echo -e "\n***\n*** Specified mount folder $TRITON_AZURE_MOUNT_DIRECTORY was not cleared properly. \n***" | ||
ls -A $TRITON_AZURE_MOUNT_DIRECTORY | ||
exit 1 | ||
fi | ||
Comment on lines
+201
to
+206
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I may be misunderstanding, but isn't the point of this feature to deterministically cache cloud storage models/files for re-use across server runs? If we clean it up after server exit, what's the point of picking a specific directory if it can't be re-used? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's a good point. The emphasis of the ticket was mostly on specifying the non-random name for the local cache directory. By default, it was mounting to |
||
|
||
rm -rf $TRITON_AZURE_MOUNT_DIRECTORY | ||
unset TRITON_AZURE_MOUNT_DIRECTORY | ||
|
||
# Add test for explicit model control | ||
SERVER_LOG=$SERVER_LOG_BASE.explicit.log | ||
CLIENT_LOG=$CLIENT_LOG_BASE.explicit.log | ||
|
Uh oh!
There was an error while loading. Please reload this page.
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.
I think we usually refer to Amazon storage as "S3", so it might be more appropriate to name the environment variable as
TRITON_S3_MOUNT_DIRECTORY
rather thanTRITON_AWS_MOUNT_DIRECTORY
.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.
I was mostly inspired by what we use now, and environmental variables were using
AWS
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.
Double checking: "AWS" is used on environment variables and "S3" on everywhere else, but the environment variable names (i.e. "AWS_SECRET_ACCESS_KEY") are specified/used by the S3 client initially, so I think it is up to you if you want to use "S3" or "AWS" on the environment variable name.