Presentations
For people who know htrflow and want to see what runs it at archive scale.
A deck opens in the browser as a presentation (arrow keys move, F goes
full screen) or downloads as a PDF.
| Deck | What it covers | Open |
|---|---|---|
| Distributed htrflow | From one machine to many nodes, a rough architecture, a pod per archival volume, a Job per campaign, the window and the queue, priority, the bucket, git as the interface, the status page and the viewer | slides · PDF |
| A possible future: DRA and KAI | What the platform could do if GPUs were described, not counted: claiming a card by what it is, splitting and sharing cards, team queues that lend and take back, a window that is a range, and how Kueue and KAI Scheduler would fit | slides · PDF |
The decks are built from Markdown in
the repository's docs/slides with Marp, on every change to the main
branch.