Using a resource allocation: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 85: Line 85:


<!--T:26-->
<!--T:26-->
If you have substantial amounts of data to transfer to an Alliance cluster in order to use your storage allocation, we strongly recommend the use of [[Globus]] for this transfer.  
If you have substantial amounts of data to transfer to an Alliance cluster in order to use your storage allocation, we strongly recommend the use of [[Globus]].  


==== <code>/project</code> ==== <!--T:27-->
==== <code>/project</code> ==== <!--T:27-->
Line 127: Line 127:


<!--T:39-->
<!--T:39-->
RAP membership is represented as a group in LDAP. It defines a group of users that are authorized to submit jobs against the RAPI (which is the Id of the RAP) and share files within the same Unix group.
RAP membership is represented as a group in LDAP. It defines a group of users that are authorized to submit jobs against the RAPI (which is the ID of the RAP) and share files within the same Unix group.


=== Using a compute allocation === <!--T:40-->
=== Using a compute allocation === <!--T:40-->
Line 140: Line 140:


<!--T:44-->
<!--T:44-->
If you have substantial amounts of data to transfer to the cluster in order to use your storage allocation, we strongly recommend the use of [[Globus]] for this transfer.  
If you have substantial amounts of data to transfer to the cluster in order to use your storage allocation, we strongly recommend the use of [[Globus]].  


==== <code>/project</code> ==== <!--T:45-->
==== <code>/project</code> ==== <!--T:45-->
rsnt_translations
57,772

edits

Navigation menu