Automation

A hands-on walk through NetBox 4.7.2 with an estate loaded into it rather than an empty demo. What each screen holds and what you do with it: rack elevations, cable traces, the IPAM tree, dual-stack interfaces, and the cabinet that turns out to be 90.7 per cent full of power while only 28.6 per cent full of kit. How to stand one up as a container stack and on a host from the packages, both run end to end. The order you have to fill it in, derived from which foreign keys are actually mandatory. How one install is carved into customers so another customer’s device returns 404 and an ungranted object type returns 403. Config contexts and the inheritance that makes them worth more than custom fields. Adding your own values to NetBox’s own status menus. Three ways to add the object your business runs on, including a datastore modelled with no code. How to write validation rules and validator classes so the database refuses what your house standard forbids. And the story of the 2021 fork that produced Nautobot, what it was for, and what has since converged. Plus driving the whole thing from the netbox.netbox Ansible collection, where the inventory is a query rather than a file and one module argument quietly allocates a new address every time it runs.

Reading a vSphere estate with the dynamic inventory, mirroring its VLANs into Proxmox SDN, and rebuilding every VM as a diskless shell before a single disk moves. Why every VMware info module hides the one field the migration needs, why vlan_id is three different types, and why one NFS export mounted twice turns the cutover into a local read.

The community.proxmox collection is an API client, not a configuration agent, and that changes the shape of every playbook that uses it. Where the tasks actually run, why proxmox_kvm declines to converge rather than updating, why proxmox_disk and proxmox_nic are where disk and NIC changes belong, and the undocumented return value you will end up needing.