To document servers, ISPs, IPAM, especially for 172.27. network, we're starting to use NetBox.
Description
Revisions and Commits
rOPS Nasqueron Operations | |||
D2790 WIP: Generate a pillar from NetBox information | |||
D3196 | rOPSf0687aecd31b Create PostgreSQL database for NetBox | ||
D2782 | rOPS4278f3440365 Document hypervisor versions |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Unknown Object (Maniphest Task) | |||||
Open | DorianWinty | T1762 Deploy NetBox | |||
Open | None | T1903 Ensure PostgreSQL service is configured by role dbserver-pgsql |
Event Timeline
Dorian configured NetBox on WindRiver, and both of us populated with current/desired configuration.
Python application, needs a dedicated Redis instance for 2 databases, PostgreSQL (it can uses db-A-001 cluster).
Dorian is seriously considering to deploy it on Docker, I've some reservations for core tools to be more complicated to get up if an accident occurs, but devcentral is already Dockerized.
Access
Access will be private to ops, as it contains personally identifiable information, like contact information for ops.
That means we've to consider export data to publicly available views, especially the one superseding wiki pages, like IP blocks.
Salt integration
I've configured Salt to access it (that works), but an issue exists when populating pillar data to minions (minions don't have it).
WindRiver doesn't start PostgreSQL, Redis, NetBox services on boot.
Services:
- PostgreSQL and Redis packages already provide a service.
- For NetBox, we can use P339
Configuration:
- PostgreSQL: role roles/dbserver-pgsql should take care of write postgres_enable="YES" to /etc/rc.conf.d/postgres
- Redis: need a role, or a unit in devserver role
- NetBox: need a role
Created this week-end a netbox database on db-A-001.
I'd suggest we setup a replication db-A-001 -> WindRiver for that db, so we've a backup copy on our PostgreSQL cluster.
Reference: https://www.postgresql.org/docs/15/logical-replication.html