ilker/rollcall
1
0 Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases 5 Wiki Activity

INSTALL: point at NetBox device sync and the lab NetBox
CI / agent (push) Successful in 3s
Details
CI / site (push) Successful in 2s
Details
CI / go (push) Successful in 42s
Details

Browse Source 
Closes #10

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-10-30 22:21:54 +01:00
1 parent dc6eb55b26
commit eb2b7baa9f
1 file changed
+2
Download Patch File Download Diff File Expand all files Collapse all files
INSTALL.md
+2
View File
@@ -149,6 +149,8 @@ region's version.
## Integrations ## Integrations
- **NetBox (or Infoblox) as the address authority.** `ipam` in `config.json`: see README, External IPAM. - **NetBox (or Infoblox) as the address authority.** `ipam` in `config.json`: see README, External IPAM.
With NetBox, `ipam.device_sync` also keeps the machines as devices (README, Devices in NetBox);
`lab/netbox/install.sh` sets up a throwaway NetBox for trying it.
- **The site's DHCP server keeps the addresses (proxy DHCP).** `dhcp_reservations` writes machines' - **The site's DHCP server keeps the addresses (proxy DHCP).** `dhcp_reservations` writes machines'
planned addresses there as fixed leases (Kea 3.0+, OpenWrt): see README, Fixed leases. planned addresses there as fixed leases (Kea 3.0+, OpenWrt): see README, Fixed leases.
- **DNS names without an IPAM authority.** `dns` in `config.json` (PowerDNS API or RFC 2136 - **DNS names without an IPAM authority.** `dns` in `config.json` (PowerDNS API or RFC 2136