-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add support for load-balanced RStudio setups #3
Comments
Approach 2 - Establish strict ohmage username conventions Only usernames that are in the form: Use a hash function that uses the usernames in above format to generate uid. |
Going with the second approach, a configuration file may be needed to define the allowed prefixes. It could be a JSON array (ordered) with implicit offset generation. Format: {
"allowed_prefixes": [ "lausd", "cvuhsd", "swhsd" ],
"offset_multiplier": 1000000
} The offset may be calculated with the following sample function: ( offset_multiplier, prefix_array_index ) => offset_multiplier * (prefix_array_index + 1) The result of this function will then be added to the "digits" in the username to generate uid. Since usernames are unique in ohmage, it can be guaranteed that there will be no collisions in the generated uids. |
Approach #1 with minimal changes to ohmage |
From RStudio requirements,
Currently, the linux account UIDs are auto-generated.
Changes needed:
Approach 1 - Requires code changes in ohmage
A new attribute should be added for ohmage users. This attribute could be calculated from within ohmage (perhaps just use the numeric
id
in the MySQLohmage.user
table).The text was updated successfully, but these errors were encountered: