Infoblox WAPI driver for the IPAM authority
CI / agent (push) Successful in 3s
CI / site (push) Successful in 2s
CI / go (push) Successful in 41s

ipam.provider infoblox: one record:host per address, named by its DNS
name and configured for DNS in dns_view ("-" = IPAM only); ownership is
the rollcall_machine extensible attribute, changed with extattrs+ so a
host's other attributes stay. Anything else on the address (a host, a
lease, a fixed address, a DHCP or reserved range, network/broadcast) makes
it taken. Delegated networks carry the rollcall attribute. WAPI paging.

The reconcile no longer compares fields an authority does not keep
(Infoblox has no prefix length or status on a host). Built from the WAPI
reference and tested against a fake WAPI; no real grid yet.

Closes #11

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-10-30 23:22:17 +01:00
1 parent eb2b7baa9f
commit 008fa3f66f
7 files changed
+731 -9

No files matched your search

+36 -3
View File
@@ -744,7 +744,7 @@ Verified in the lab: Debian 13 (with a bond and VLAN), Rocky 9 and AlmaLinux 9
dual-stack on two segments, AAAA lookups through dnsmasq, the admin CLI over
`https://[fdc3:...]`.
## External IPAM (NetBox; Infoblox-style)
## External IPAM (NetBox, Infoblox)
Rollcall works on its own, but at a site with an established network plan the
address authority is somewhere else. With `ipam` in `config.json` every
@@ -822,9 +822,42 @@ 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.
### Infoblox
The same contract over Infoblox WAPI (v2.12 by default; give a full
`.../wapi/vX.Y` URL for another):
```json
"ipam": {
"provider": "infoblox",
"url": "https://gm.example.com",
"user": "rollcall",
"password_file": "/etc/rollcall/infoblox.pw",
"ca_file": "/etc/rollcall/infoblox-ca.pem",
"dns_zone": "int.example.com",
"network_view": "default",
"dns_view": "default"
}
```
- **One host record per address.** Named by its DNS name (`rollcall-<address>`
without one) and configured for DNS in `dns_view`, so Infoblox publishes the
A/AAAA record itself; `"dns_view": "-"` keeps them IPAM-only. The zone must
exist in that view.
- **Ownership** is the extensible attribute `rollcall_machine` (define it in
the grid as String). Rollcall changes it with `extattrs+`, so a host's other
attributes stay; hosts without it are never changed or deleted.
- **Taken** is anything else on the address: another host, a lease, a fixed
address, a DHCP or reserved range, the network or broadcast address.
- **Delegated networks** carry the extensible attribute `rollcall` (any value;
define it as String); `Site` and `VLAN` attributes are shown when present.
- The WAPI user needs read/write on host records and read on networks and
IPv4/IPv6 addresses in the network view (and the DNS view when publishing).
Device sync (above) is NetBox-only.
The provider is an interface (reserve, owned records, update, delete,
delegated prefixes); the NetBox driver is the first. An Infoblox WAPI driver
maps them to `record:host`/`fixedaddress` with extensible attributes.
delegated prefixes) with the NetBox and Infoblox drivers.
## DNS provider (PowerDNS, RFC 2136)