Wiki TODO

This page lists Anunna documentation that has been published but still needs current or authoritative information filled in. The pages below are usable as they stand, but each contains placeholders — marked in the page source with comments — where someone with current operational knowledge needs to add or confirm details.

To pick up a task: open the page, find the TODO comment(s) in its source, add the information, and remove the item from this list.

Hardware and network

• Cluster Architecture Overview — confirm the current interconnect (Omnipath and/or InfiniBand) and topology; add a current architecture diagram (the old schematics were out of date and were removed).
• Compute Hardware Overview — fill in the per-node specifications: number of CPU nodes, cores and memory per node, CPU model(s), and whether there are high-memory "fat" nodes; number of NVIDIA GPU nodes, GPUs per node, and host CPU/memory; AMD GPU model and node details.
• Network & Security — confirm the interconnect (as above) and document the data-security posture: how data is protected at rest and in transit, access control, handling of confidential or personal data, and backup/retention.

Storage

• Quotas — document the Lustre quota model (per-user or per-group, and the default sizes for /lustre/backup, /lustre/nobackup, /lustre/scratch), the command(s) users run to check their current usage, and how to request more space. Only the home-directory quota (200 GB) is currently documented.

Policy and governance

• Mission and Governance — confirm and document the current governance bodies (for example a steering group and user group) and their membership. The previous roster was from the Breed4Food era and was removed.
• Roadmap — add the current roadmap, or link the latest roadmap document. The 2019–2020 version was removed.
• Sustainability — add the sustainability / green-HPC policy and any concrete measures: energy sourcing, cooling, hardware lifecycle, and institutional targets.
• Policies and Terms of Use — supply the formal terms of use / acceptable-use policy (data ownership and responsibilities, security obligations, consequences of misuse) and confirm the current account-request route and per-group access contacts. The previous access-contact list was from the Breed4Food era and was removed.

Nice to have

• FAQ — extend with the questions the HPC team is asked most often (for example quota limits, GPU access, course accounts, data transfer).

See also

• Support