Bureaucrats, cc_docs_admin, cc_staff
2,879
edits
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
<!--T:9--> | <!--T:9--> | ||
Having to share some but not all of your data with a colleague or another research group is a common occurrence. Compute Canada systems provide a variety of mechanisms to facilitate this data sharing with colleagues. If the person you want to share the data with is a member of the same research group as you, then the best approach may be to make use of the [[Project_layout | project space]] that each research group has in common. At the opposite extreme, if the person you need to share the data with doesn't even have an account on the cluster, you can use use [[Globus]] and in particular what is called a [[Globus#Globus_Sharing | shared endpoint]] to share the data. To handle the scenario of sharing with a colleague who has an account on the cluster but doesn't belong to common research group with you, the simplest approach is to use the permissions available in the filesystem to share the data, the principal topic of this page. | Having to share some but not all of your data with a colleague or another research group is a common occurrence. Compute Canada systems provide a variety of mechanisms to facilitate this data sharing with colleagues. If the person you want to share the data with is a member of the same research group as you, then the best approach may be to make use of the [[Project_layout | project space]] that each research group has in common. At the opposite extreme, if the person you need to share the data with doesn't even have an account on the cluster, you can use use [[Globus]] and in particular what is called a [[Globus#Globus_Sharing | shared endpoint]] to share the data. To handle the scenario of sharing with a colleague who has an account on the cluster but doesn't belong to a common research group with you, the simplest approach is to use the permissions available in the filesystem to share the data, the principal topic of this page. | ||
<!--T:12--> | <!--T:12--> | ||
When sharing a file it's important to realize that the individual you want to share it with must have access to the entire chain of directories leading from <code>/scratch</code> or <code>/project</code> to the directory in which the file is located. If we consider the metaphor of a document locked in a safe in the bedroom of your apartment in a large building, giving me the combination to the safe will not allow me to read this document if I do not also have the necessary keys to enter the apartment building, your apartment and finally your bedroom. In the context of a filesystem, this means having | When sharing a file it's important to realize that the individual you want to share it with must have access to the entire chain of directories leading from <code>/scratch</code> or <code>/project</code> to the directory in which the file is located. If we consider the metaphor of a document locked in a safe in the bedroom of your apartment in a large building, giving me the combination to the safe will not allow me to read this document if I do not also have the necessary keys to enter the apartment building, your apartment and finally your bedroom. In the context of a filesystem, this means having execute permission for each directory between the root (e.g. <code>/scratch</code> or <code>/project</code>) and the directory containing the file. | ||
==Filesystem permissions== <!--T:1--> | ==Filesystem permissions== <!--T:1--> |