Version: v6.0.0 [Falcon]

brc config ru list

List the Radio Units known to the cluster

Synopsis

List every Radio Unit the cluster knows about, joining the two places that knowledge lives.

Declared entries come from /etc/pontus/ru.json on each worker node. This is what the operator asked for, and it is read over SSH.
Observed entries come from the radio.gaia.t9s.io/inventory annotation Pontus publishes on the node. This is what Athena can actually assign to an Access network element, and it is read with the Kubernetes credentials.

The listing is keyed on the Radio Unit, not on the node. A unit sitting on a fronthaul segment that several workers are attached to is reachable from each of them, and Pontus publishes it on every one, so such a unit occupies a single row whose per-node columns are stacked in step with the node column.

That is worth reading closely: a Radio Unit visible from more than one node is a single piece of hardware that Athena sees as several assignable resources, one per node, and nothing stops two Access network elements on two different nodes from each claiming it.

An entry that is declared but never observed is the ordinary symptom of a fronthaul problem: the unit does not answer on the fronthaul VLAN, PTP has not locked, or the credentials in ru-secrets are wrong. The reason column carries whatever ru.py reported, which is usually enough to tell those apart.

An entry that is observed but not declared means the annotation is stale: Pontus republishes on a fifteen second interval, so this clears on its own shortly after a unit is removed from the inventory.

Reading the declared inventory needs SSH access to the worker nodes. Pass --observed to skip it and report only what Pontus published, which needs nothing but the kubeconfig.

brc config ru list [flags]

Examples

# every Radio Unit on every worker node
brc config ru list

# only the Radio Units reachable from one node
brc config ru list --node moto

# skip the SSH round trip and report only what Pontus published
brc config ru list --observed

# machine readable output
brc config ru list --output json

Options

  -h, --help            help for list
      --host string     SSH host of the worker node when it differs from the Kubernetes node name
      --node string     only report the Radio Units reachable from this worker node
      --observed        report only what Pontus published, without reading the nodes over SSH
  -o, --output string   output format: table or json (default "table")
      --user string     SSH user for the worker node

Options inherited from parent commands

  -n, --namespace string   namespace to perform the operations (default "trirematics")
  -v, --verbose            debug output

brc config ru list