InfraGraph CLI

InfraGraph provides a command-line interface (CLI) built with Typer for converting system descriptions into InfraGraph format and visualizing infrastructure topologies.

Installation

pip install infragraph

Alternatively, clone the repo and build:

git clone https://github.com/Keysight/infragraph.git
cd infragraph
make clean
make install

Or download the .whl from releases and install directly:

pip install infragraph-<version>.whl

Once installed, the infragraph command is available in your terminal.

Commands

`translate`

Convert output from supported system tools into an InfraGraph YAML or JSON definition.

infragraph translate <tool> -i <input_file> -o <output_file> --dump <format>

Argument / Option	Description
`tool`	Translator to use (e.g., `lstopo`)
`-i`, `--input`	Path to the input file
`-o`, `--output`	Output file path (default: `dev.yaml`)
`--dump`	Output format — `yaml` or `json` (default: `yaml`)

Supported translators: lstopo

Example — convert an lstopo XML export to InfraGraph YAML:

infragraph translate lstopo -i lstopo_output.xml -o my_device.yaml --dump yaml

`visualize`

Generate an interactive HTML visualization from an InfraGraph infrastructure definition.

infragraph visualize -i <input_file> -o <output_dir> [--hosts <hosts>] [--switches <switches>]

Option	Description
`-i`, `--input`	Path to the InfraGraph YAML/JSON file
`-o`, `--output`	Output directory where the visualization will be generated
`--hosts`	Comma-separated device names to render as hosts
`--switches`	Comma-separated device names to render as switches

Example — visualize an infrastructure with host and switch hints:

infragraph visualize -i my_infrastructure.yaml -o ./viz --hosts "dgx_a100" --switches "leaf_switch,spine_switch"

Then open ./viz/index.html in a browser. The visualizer produces a multi-level view: a top-level graph of instances and inter-device connectivity, with drill-down into each device's internal components (xPUs, NICs, CPUs, memory, PCIe topology, etc.). For large topologies the visualizer can compress the infrastructure view. A Compressed button appears in the header for fabrics with more than 128 hosts. It merges nodes that have identical connectivity into a single node, and a slider next to it chooses how aggressively, from merging equivalent neighbours up to one node per tier. Groups are named from the data: a bottom-tier group whose members all uplink to one switch is shown as a rack, and several such racks merged is shown as a pod.

Clicking a rack or pod opens it rather than jumping straight into a device template. You see its actual member servers together with the switches they uplink to, and a hop slider controls how much surrounding fabric comes with them. Clicking a server there drills into that device's internals as usual, so the trail reads Infrastructure, then rack, then device. Switch groups behave differently and go straight to the device template, because every switch in a group is an instance of the same device. At the highest compression rungs a single node can stand for every server in the fabric, and those are left closed since expanding one would build thousands of nodes; lower the compression to reach a group you can open. Passing --hosts helps the visualizer identify the bottom tier.