NetBox's web UI through Rollcall, and links to it from the web UI
CI / agent (push) Successful in 3s
CI / site (push) Successful in 3s
CI / go (push) Successful in 42s

With NetBox as the IPAM under a path (its BASE_PATH) and ipam.url
carrying it, Rollcall serves NetBox's UI at that same path, for admins
only (the admin certificate, as for the API); NetBox keeps its own
login. Redirects that name NetBox's own address are turned back to
Rollcall's, Rollcall's credentials are not passed on. NetBox opens
wherever Rollcall does: a lab NetBox on a segment the browser cannot
reach, say.

The web UI links to NetBox: the sidebar, sites, rooms, racks, switches
and a machine's device (by its rollcall_machine field). ipam.ui_url
points the links at NetBox directly instead.

NetBox paging under a BASE_PATH doubled the path on the next page
(the next link carries it already); fixed. The lab NetBox moves under
/netbox/ and trusts the region's addresses for its forms.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-11-01 12:21:22 +01:00
1 parent c31a89482e
commit cc1245da1e
11 files changed
+214 -12

No files matched your search

+31
View File
@@ -878,6 +878,37 @@ The NetBox user needs `view/add/change/delete` on `dcim.device`,
`dcim.devicetype` and `dcim.devicerole`, and `view` on `dcim.location` and
`dcim.rack`, on top of the IPAM permissions.
### NetBox's UI through Rollcall
When NetBox runs under a path (its `BASE_PATH`, e.g. `BASE_PATH = 'netbox/'`)
and `ipam.url` carries it (`"url": "https://netbox.example/netbox/"`), Rollcall
serves NetBox's web UI at that same path, `https://<rollcall>/netbox/`, for
admins only (the admin certificate, as for the API). NetBox keeps its own login.
This opens NetBox wherever Rollcall opens, also when the browser cannot reach
NetBox itself. Two settings on the NetBox side:
```python
BASE_PATH = 'netbox/'
CSRF_TRUSTED_ORIGINS = ['https://rollcall.example'] # where browsers post from
```
The web UI then links to NetBox: the sidebar, a site, room and rack on the Sites
pages, a switch, and a machine's device. `ipam.ui_url` points those links
elsewhere (NetBox reached directly) when that is preferred; a NetBox at the root
of its host gets links to `ui_url` only.
### Cabling and switches
`GET /api/v1/cabling` gives each located machine's ports and the switch port
each is plugged into, from the LLDP its commissioning saw (`lldpd` in the
commissioning image). A switch's place is NetBox's (the device with that name,
its rack and position, read with the layout on every reconcile; the NetBox user
needs `view` on `dcim.device`) or set by hand (`POST /api/v1/switches
{"name","building","room","rack","unit"}`, which NetBox does not move; `DELETE
?name=` forgets it). The 3D room draws the backs of the servers, the switches
and the cables; a switch with no place is drawn where most of its cables are,
marked as estimated.
### Infoblox
The same contract over Infoblox WAPI (v2.12 by default; give a full