Search the docs

Prerequisites

Configuration Management with Teams & Admins

Ensure other teams/admins with control over storages nodes, especially Tier 0/GPU nodes, do not take control of drives used for Tier 0 and reformat or remount. One option is to let them dictate mount point, and agree to how much space will be used for different purposes. Hammerspace can configure thresholds to comply with usage guidelines.

Repository Access

Since several packages need to be installed, access to a repository containing the packages is essential. Sites without internet access will have to establish their own repos that include packages used through Tier 0 deployment procedures. Note package requirements for basic LSS /Tier 0 node deployments, as well as for additional components such as data movers. Requirements include RPM style packages as well as modules for Python scripts, and, of course, software provided by Hammerspace.

Packages for Tier 0 Nodes

  • mdadm

  • mkfs.xfs (Not installed by default on some distributions)

  • nfs-server

  • If using RDMA and Intel or Broadcom NICs, the OEM driver is required. Do not use the Linux distribution inbox driver.

Kernel Management

To ensure stability and compatibility with Hammerspace’s upstream NFSv4.2 enhancements, follow these kernel guidelines:

  • Use Validated Kernels: Recommended versions include RHEL 8, 9 or 10. If possible, do not use the Ubuntu 6.8 kernel for Tier 0 nodes. It lacks upstream LTS support and back-ports from standard kernel processes.

  • Preferred LTS Releases: If not using RHEL, stick to Kernel.org Long Term Support (LTS) releases such as 5.15, 6.1, 6.6, or 6.12.