User Accounts on OSBv2#
Users need to register and log in to OSBv2 to open a workspace in any of the applications: NWB Explorer, NetPyNE or JupyterLab.
Registration#
OSBv2 has a different user database to OSBv1
Currently there is no overlap between the user database of OSBv1 and OSBv2. You will need to create a new user account to use OSBv2.
To register for an OSBv2 user account click here.
Signing in#
Once registered, users can sign in by clicking the link on the top right of the homepage, or by clicking here.
User data storage inside a workspace#
Warning about user storage
Note: while we will endeavour to securely store and backup all data during the life of the OSB project (we do our work on the platform too!) we do not currently offer any guarantees, and so encourage users to back up any valuable research data regularly.
There are a number of locations where data can be stored when a workspace is opened:
Location |
Description |
Persistence |
---|---|---|
|
A private volume which is accessible for this user on every workspace they open |
Persistent* |
|
A volume which is accessible every time this workspace is opened (even when workspace is shared and opened by another user - it will be readonly in this case) |
Persistent* |
|
A link to |
Persistent* |
|
Local storage to use while using the workspace |
Temporary^ |
|
Location for Python packages (those preinstalled and those installed during this session). Note: this is renewed every time the workspace is reloaded, so new packages will need to be installed every session |
Temporary^ |
* See warning above on user storage.
^ Note: if a workspace is closed, and then opened in the same application shortly afterwards, the same Kubernetes pod may be used, along with the same transient storage, which may result in data on /opt/home
and /opt/conda
persisting between these sessions.
The easiest way to browse these locations is by opening the JupyterLab application, where other files can be uploaded and existing files downloaded.
User quotas#
Currently there are no user quotas imposed on storage or numbers of workspaces while we are in beta testing. However, we are planning to incorporate these as the resource grows in size.