-
Notifications
You must be signed in to change notification settings - Fork 155
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
Provide User Storage to Researchers across Windows and Linux VMs #1566
Comments
@marrobi to add a little more detail to this |
@marrobi is this an accurate reading of the requirements...?
|
sorry...should have numbered that list to make it easier to discuss (done) |
Correct, add to no 3 - "shared across all their VMs" |
On the file system previously used a users object id as the azure file share name. |
I'm assuming that a user does not know their objectid though? Do you mean their AAD objectid |
If we mount the same shared storage to each VM, can't users create their own folder structure there? |
I agree @tamirkamara. If they have shared storage, the folder structure they create (whether it be based upon usernames or otherwise) is up to them. @marrobi other than the convenience of knowing "when I join a workspace I can assume there's a folder with my name on it" is there some other reason we need to do this? |
Two scenarios that need covering. Although wouldn't priotise this, has been asked for, but not a blocker.
First one is more pressing as think it will be an issue before long. |
As a Workspace User I want a storage area for my sole use, mounted into my virtual machine, so that I have my own space to work in.
Note:
Although this storage needs to be workspace specific it does not need to be private to the user, as the workspace is the security boundary. Although private storage for each user within a workspace has been discussed with users, after discussion it has been deemed not appropriate.
Acceptance criteria:
Open to suggestions as to what "home directory" means, and as to what is appropriate.
The text was updated successfully, but these errors were encountered: