GreenRay AIO
Hands-on lab simulator and mock exam for the NVIDIA-Certified Professional: AI Operations (NCP-AIO) exam.
GreenRay AIO drops you into a broken or half-configured four-node DGX H100 cluster managed by Base Command Manager and asks you to find out what is wrong and fix it, with the commands you would use on real systems: nvidia-smi, dcgmi, Slurm, kubectl and helm with the GPU Operator, cmsh, InfiniBand tools, Docker and NGC. It grades the end state of the cluster, not the commands you typed. No GPU, no cloud account, nothing but Python.
root@bcm-head:~# ssh dgx-03
root@dgx-03:~# dmesg | grep -i xid
[ 8812.402113] NVRM: Xid (PCI:0000:5d:00): 79, pid=0, GPU has fallen off the bus.
root@dgx-03:~# nvidia-smi
Unable to determine the device handle for GPU00000000:5D:00.0: Unknown Error
root@dgx-03:~# check
PASS you read the kernel log on dgx-03
.... 2 more success criteria not met yet
Install
uv tool install greenray-aio # or: pipx install greenray-aio
greenray next
Or with Docker, keeping your progress in a named volume:
docker run -it --rm -v greenray:/home/lab/.greenray ghcr.io/rehmanayounis/greenray-aio
Python 3.10 or newer on Linux, WSL, macOS or Windows. See Getting started for the details and your first lab.
How it works
- 48 scenarios cover every topic of the exam blueprint (coverage map), from a six-lab on-ramp for the basics to multi-node incidents.
- Guided or incident mode. Guided shows the objectives and hints. Incident mode shows only the ticket; the root cause stays hidden until the debrief, which then gives you the reference solution, the edge cases and your own commands side by side.
- A grader that reads state. Any valid fix passes. Evidence checks confirm you diagnosed before you changed things.
- A study path.
greenray nextsays what to practise,greenray planlays out four weeks, and every mock exam ends with a report card. - A mock exam in the current format: 30 questions plus 3 labs on Slurm, Kubernetes and BCM in 120 minutes, and a labs-only mode for pacing.
- A terminal that behaves like a node:
--helpandmanpages, your real editor fornanoandvim, tab completion, history,watch, livedmonsamples.
Documentation
The full manual is at rehmanayounis.github.io/greenray-aio:
- Getting started: install and your first ten minutes
- Using the lab: every command, the lab meta-commands, what the grader judges, settings
- Study path: the on-ramp,
nextandplan, the mock exam and its report card - The simulated cluster: hosts, tools and limits
- Writing scenarios, Architecture, Contributing, Security, Changelog
Licence and trademarks
Apache-2.0; see LICENSE and NOTICE.
GreenRay AIO is an independent study tool. It is not affiliated with, endorsed by or sponsored by NVIDIA. NVIDIA, DGX, Base Command Manager, NCP-AIO and related names are trademarks of NVIDIA Corporation, used only to describe the certification this tool helps you prepare for. The scenarios and questions are original work written from public documentation; nothing is taken from the exam.
Metadata
Release files for greenray-aio 0.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| greenray_aio-0.9.0.tar.gz | 536.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| greenray_aio-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / greenray_aio-0.9.0.tar.gz
| Download URL | greenray_aio-0.9.0.tar.gz |
|---|---|
| Size | 536.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
16f455c80f8d415d218d97dd715da44d7b19528952b3d062e99ba7c0670c1185
|
|
BLAKE2b-256 checksum How to use checksums |
fc9334fdaba8ddc6483bfec1a3e31d9c97f11bc27983bbca9732d0bb7fe419d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logRelease files / greenray_aio-0.9.0-py3-none-any.whl
| Download URL | greenray_aio-0.9.0-py3-none-any.whl |
|---|---|
| Size | 681.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6e5a9cdc5b71d1cf6c95d8a835abdb332dfbced9b4a35cd4afa3992cfb90d428
|
|
BLAKE2b-256 checksum How to use checksums |
d3fd3d447fa7a071a1d826e16b959e708e24fca94d017f2d432a6b932eb7bb73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logSecurity for greenray-aio 0.9.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for greenray_aio-0.9.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.