CCR accounts are available to UB faculty, their collaborators and students either working with them or in a class that requires access to CCR. Account requirements and application info can be found here: http://www.buffalo.edu/ccr/support/ccr-help/accounts.html
ALLOCATIONS TO RESOURCES:
All access to CCR resources (clusters, servers, research cloud, project storage, software licenses) is granted and revoked via allocations. Allocations are managed by PIs in ColdFront (https://coldfront.ccr.buffalo.edu). Users should login to ColdFront to see what allocations they have access to and when they expire. Faculty should renew allocations before expiration. If an allocation expires, any user on that allocation will be no longer be able to access that resource. Expired allocations can't be renewed. A new allocation request must be submitted to gain access to the resource again. More details can be found in the ColdFront documentation.
YEARLY PROJECT REVIEW: Faculty are required to review their projects and verify all accounts in their group on a yearly basis. If the project is not renewed within 6 months of the expiration date of the newest allocation on that project, all accounts in the group will be deactivated for security reasons. If there is no activity for one year, data and accounts associated with the project will be deleted
- Account - When a faculty member leaves the University, access to the UB network will be removed as soon as your employment ends. Unless arrangements have been made, your CCR account will be terminated at the same time as your UB account.
- Data – All data owned by your account on our systems will be deleted within 30 days of account termination. This includes data on CCR’s network attached storage systems (user & project directories), scratch directories (scratch directories on local compute nodes and GPFS scratch), budget storage directories (if applicable), data stored on servers owned by the faculty group (if applicable), and cloud instances and storage (if applicable).
IMPORTANT: When a faculty member leaves behind students at UB, arrangements MUST be made with those students and another faculty member to take over their account sponsorship. Student accounts must be sponsored by an active faculty group, so unless prior arrangements have been made, when a faculty member leaves, any accounts sponsored by them are also terminated and data is removed.
STUDENTS – Class Accounts:
- Account – Accounts provided for class work are valid for the semester that the class is offered in and automatically terminated at the end of the semester. If a student requires additional time to complete coursework, the professor teaching the course must contact CCR help to request an extension on the account. Student accounts that are also sponsored by a faculty member remain active after the course ends, subject to the policies in the “faculty sponsored accounts” section below.
- Data – Data in a student’s home directory created for a class account is deleted 30 days after account termination. This includes data on CCR’s network attached storage systems (user & course project directories), scratch directories (scratch directories on local compute nodes and GPFS scratch), and cloud instances and storage (if applicable).
- Usage - Usage of the cluster by students in a class is reported back to the instructor of the class. Requests for assistance, software installations, or other communications by students to CCR staff could potentially be shared with the instructor.
STUDENTS – Faculty Sponsored Accounts:
- Account – An account sponsored by a faculty member is terminated when a student leaves the University at Buffalo or when the sponsoring faculty member requests the student’s access to CCR be removed. If a faculty member wants a student to continue to access CCR resources after leaving the university, a request must be made to CCR help. The account will then be moved under the “non-UB collaborator” category of accounts (see below).
- Data - Data stored on CCR’s network attached storage systems in the user’s home directory and scratch directories (scratch directories on local compute nodes and GPFS scratch) are deleted when the student’s account is terminated. If there is data stored by the student in a faculty member’s project directory, budget storage directory, or cloud project, this data is not removed. It is up to the faculty member to manage the data in their project spaces.
- Usage - Usage of the cluster by students is reported to the faculty member sponsoring the student's account. Requests for assistance, software installations, or other communications by students to CCR staff could potentially be shared with that faculty member as well.
- Account – Accounts granted to non-UB collaborators are dependent on the sponsorship of a UB faculty member. If at any time, the sponsor of your account wants your access to CCR resources cut off, we are required to terminate the account.
- Data - Data stored on CCR’s network attached storage systems in the user’s home directory and scratch directories (scratch directories on local compute nodes and GPFS scratch) are deleted when the account is terminated. If there is data stored by the collaborator in a sponsor’s project directory, budget storage directory, or research cloud, this data is not removed. It is up to the sponsor (UB faculty member) to manage the data in their project spaces.
RESEARCH CLOUD: All above policies apply to cloud accounts, in addition to the following:
- Account - Access to the research cloud is granted through request and payment of a cloud subscription. Users must have a CCR account to access the research cloud. As stated in our research cloud policies, failure to maintain an active payment for cloud usage will result in the termination of cloud account access. Please review this article for more details: https://ubccr.freshdesk.com/solution/articles/5000680817
- Data – If the account owner does not respond to CCR payment requests within 30 days, a final bill will be sent for the overage charges and all information/data associated with the cloud account will be deleted - this includes: instances (running & terminated), all data (including, but not limited to, S3 buckets, volumes, and snapshots), ssh keys, elastic IPs, load balancers, custom images. This is a permanent action. Data in the cloud is not backed up and therefore, not retrievable once deleted.
MISUSE OF SYSTEMS: Failure to follow University at Buffalo and CCR computing policies may result in your account being removed and all data deleted. Please review this article for more details: https://ubccr.freshdesk.com/solution/articles/13000033902