uabrc / uabrc/uabrc.github.io

Hardware tables are no longer accurate

Open
#501 1 comment 0 reactions 1 assignee View on GitHub

@wwarriner is already working on this.

Since Aug 22, 2023.

fix: inaccuracy ⚠️ system: cheaha 🖧
Dominant language
Python
Stars
24
Forks
15
Avg merge
10d 3h
Merged PRs (30d)
1

Description

What is inaccurate?

This is for Cheaha.

The overall hardware table is OK.

Partition and QoS tables need updating. We've added amperenodes* partitions, including the amperenodes-debug partition. Will add and cross-link a separate issue about amperenodes-debug.

Additional needs

Some of these may be redundant with #480.

  • Hardware table name: "Historical Hardware" and move to the bottom of the page. Put active column toward the left.
  • Have a second table "Active Hardware" at the top of the page.
  • Active hardware table: add "partitions" column, contains partitions using hardware in that row, blank if none.
  • Active hardware table: move "active" column to be second column
  • Partition table: add "hardware generations" column.
  • Partition table: see #480.
  • Partition table: add "qos" column, listing all qos affecting that row's partition, by name.
  • QoS table: add information on per user vs per node. If there are rows with both, may require refining partition table.
  • See #486
  • After #486, create a "combined" hardware table and flops table in some other central location. On that page, link to the hardware pages of each fabric. Maybe also link to storage information on this central page.

Please resolve issues #480 and #486 first.

Follow up with #503.

Where is the inaccuracy?

https://docs.rc.uab.edu/cheaha/hardware/

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.