Globus Tutorials

This page is under construction, and may have missing or incomplete information. Hardhats are not required.

Logging in

To log into Globus, go to https://www.globus.org/ and click the Log in button.

Log into Globus using your USD credentials.

It should open your Globus account.

Making a Lawrence Endpoint

Select 'Endpoints' from the side menu, then the 'Shared with You' tab.

Click on 'Search all endpoints'.

Type in "sdds" then click on the 'SDDS - South Dakota Data Store' option.

Click on the 'Collections' tab.

Click on 'Add a Collection'

Click on 'SDDS - South Dakota Data Store (POSIX)'

For the next step, you will need the path to the directory to which you want to connect (e.g. home directory, lab directory, etc.): to find this, from within Lawrence, use the cd command to navigate to the desired directory, then use pwd to print your working directory.

user.name@usd.local@login ~]$ cd ~
user.name@usd.local@login ~]$ pwd
/home/usd.local/user.name

Fill 'Path' with lawrence/the_path_to/your_directory_on_Lawrence . Choose a display name, fill in other details as desired, and click 'Create Collection'.

After submitting, a confirmation window will appear. To make another collection to a directory on Lawrence, click on the 'Create another collection from SDDS - South Dakota Data Store' button.

Making a Personal Endpoint

To make a personal endpoint, click on the 'Endpoints' tab, then 'Create a personal endpoint'.

If the prompt comes up, download the Globus Connect Personal Software.

A new window for the setup should appear. Click "Log in".

Find your organization in the drop-down menu (For USD users, this will be 'University of South Dakota').

Once you have logged into your organization's login, provide a label for the endpoint and click 'Allow'.

Go to the window attached to the globus icon on your taskbar. In this window, verify your identity (possibly an email address), enter the collection name (endpoint), and enter details if desired. Also note the "high assurance endpoint" option. Then click on 'Save'.

If a high assurance endpoint is needed, other aspects of the data storage (such as storage on Lawrence) may not be equipped with the necessary security measures. Please contact RCG at rcg@usd.edu for assistance.

A message about the success of the setup should appear.

Making a Group

In the 'Groups' tab, click on 'Create new group'

Add a group name, description if desired, choose the administrator for the group, and whether the group will be viewable by anyone on Globus, or only by those in the group. Then click 'Create Group'.

The group overview will appear once the group is created.

Sharing with Other Users (Individual or Group)

Sharing an endpoint is a way to give another person access to one's own data, as explained in Globus Information: Guest Collections & Sub-Collections.

First, select the endpoint that is connected to the data to be shared (even if not all the data to which the endpoint is connected will be shared; this can be restricted in another step).

Click on the 'Sharing' tab.

Click on the 'Add Permissions - Share With' button.

The next step is separated into two paths based on whether the endpoint needs to be shared with a user or with a group. Please choose the section accordingly.

If sharing with an individual user:

Fill in the path to the directory (Note: / starts at the endpoint's location, so the path /Carrots (as per the example) in permissions for an endpoint that connects to the home directory lawrence/home/usd.local/user.name will connect to lawrence/home/usd.local/user.name/Carrots overall).

Ensure 'user' is selected, and enter the email address of the user who is to be given permissions. Make sure this email address is connected to the user's Globus account. Then click 'Add'.

Write a message if desired, choose whether to give the recipient write access, and click 'Add Permission'.

Note: Keep in mind that all the directories/files within the shared directory will be accessible to the people it is shared with (be cautious of sharing the path as is, that is, leaving it at root: / .

For this reason, we recommend making a directory called 'globus', within the home/lab directory (this must be done on Lawrence), organizing files/directories to be shared within that directory, rather than sharing the entire home/lab directory, and then sharing the 'globus' directory. (Replace 'Carrots' in this example with 'globus'.)

This should now show up under the 'Permissions' tab.

Note: If another Globus user with whom you have shared access to your endpoint adds or makes a change to a file, that action will be considered as if it was done by you.

Example: Person A shares an endpoint with person B and person B makes a new file on the shared endpoint: Lawrence will consider the file to be owned by person A.

If sharing with a group:

Fill in the path to the directory (Note: / starts at the endpoint's location, so the path /Carrots (as per the example) in permissions for an endpoint that connects to the home directory lawrence/home/usd.local/user.name will connect to lawrence/home/usd.local/user.name/Carrots overall).

Select 'group'. The window will change to a search window. Select the desired group, then (back on the first page) choose whether to give the group write permissions and click "Add Permissions".

Note: Keep in mind that all the directories/files within the shared directory will be accessible to the people it is shared with (be cautious of sharing the path as is, that is, leaving it at root: / .

For this reason, we recommend making a directory called 'globus', within the home/lab directory (this must be done on Lawrence), organizing files/directories to be shared within that directory, rather than sharing the entire home/lab directory, and then sharing the 'globus' directory. (Replace 'Carrots' in this example with 'globus'.)

This should now show up under the 'Permissions' tab.

Note: If another Globus user with whom you have shared access to your endpoint adds or makes a change to a file, that action will be considered as if it was done by you.

Example: Person A shares an endpoint with person B and person B makes a new file on the shared endpoint: Lawrence will consider the file to be owned by person A.

Last updated