Private Nodes Policy and Procedures

Purpose

The purpose of the Private Nodes Policy and Procedures is to establish clear guidelines for the request, procurement, and management of private nodes within the UTS on-prem High Performance Computing (HPC) environment. It ensures consistency, security, and operational alignment with institutional standards.

Scope

The Private Nodes Policy and Procedures applies to all users seeking to deploy private nodes in the UTS on-prem HPC environment. It covers administrative access, hardware specifications, vendor requirements, warranty terms, lifecycle management, and the overall process from approval to implementation.

1. Admin/Sudo Rights

1.1 Users will not receive admin or sudo rights for private nodes in the iHPC or HPCC.

2. Warranty and Decommissioning

2.1 The default warranty period for purchased nodes is 4 years.

2.2 At the end of the warranty period, if you choose not to renew the warranty or if it is no longer available, the node will be decommissioned and disposed of.

2.3 Approval from [Designated Authority] is required if you wish to reclaim the nodes at the end of their life (EOL).

3. General Guidelines for Private Nodes

3.1 Preferred Vendors: Dell or HPE

3.2 Server Chassis: Must meet data center specifications

3.3 Power Supply: 1800W or under, preferably redundant

3.4 Storage: Minimum of 1TB for Operating System (OS) and 2 TB for scratch space.

3.5 Specifications: Final specifications are subject to change based on data center capacity.

4. Management and Maintenance

4.1 Private nodes will be managed and maintained in the same manner as public nodes in our HPC systems.

4.2 The same backup and security measures applied to public nodes will also be implemented for private nodes.

5. Procurement and Implementation Timeline

5.1 The procurement and implementation process for private nodes typically involves several stages, including approval, purchasing, delivery, installation, and configuration.

5.2 The entire process can take several weeks to a few months, depending on various factors such as vendor lead times, data center capacity, and specific requirements.

5.3 Users will be kept informed of the progress and any potential delays throughout the process.

5.4 Setting realistic expectations regarding the timeline helps ensure a smooth and satisfactory experience.