feat: update nautobot with enriched data updated by inspect hooks

[haseebsyed12]

By leveraging Ironic's native notification system (documented at Ironic Notifications),
we can react to state changes to keep Nautobot in sync.

Subscribe to specific Ironic notification events:

Nodes:

baremetal.node.update.end / baremetal.node.create.end → create or update the node in Nautobot
baremetal.node.delete.end → remove the node from Nautobot
Ports:

baremetal.port.update.end / baremetal.port.create.end → create or update the port in Nautobot
baremetal.port.delete.end → remove the port from Nautobot
Portgroups:

baremetal.portgroup.update.end / baremetal.portgroup.create.end → create or update the portgroup in Nautobot
baremetal.portgroup.delete.end → remove the portgroup from Nautobot

We focus on .end events since those represent completed operations with consistent state, and handle create/update together since a newly created node may not have complete information initially.

Sync these Nautobot resources:

1. Device(dcim.devices) - server identity, location, rack, tenant, status
2. Interfaces(dcim.interfaces) - network ports with MAC, type, description
3. iDRAC Interface(dcim.interfaces) - management interface with BMC MAC
4. Cables(dcim.cables) - connections between server interfaces and switch ports
5. IP Addresses(ipam.ip_addresses) - BMC IP address
6. IP-to-Interface associations(ipam.ip_address_to_interface) - links BMC IP to iDRAC interface

Nautobot Device Sync Implementation Comparison

Overview

Comparison between old (nautobot_device.py) and new (nautobot_device_sync.py + nautobot_device_interface_sync.py) implementations.

Data Source

Old	New
Fetches data directly from BMC via Redfish (ChassisInfo)	Fetches data from Ironic APIs (node, inventory, ports)

Device Identification

Old	New
Uses serial_number to find/create device	Uses Ironic node uuid as device ID
Device name passed as parameter	Device name generated from {manufacturer}-{service_tag}

Switch Lookup

Old	New
Finds switches by cf_chassis_mac_address custom field via GraphQL	Finds switches by name (switch_info) or interface MAC address via REST
Includes base MAC calculation fallback for Cisco switches	No base MAC fallback

Interface Identification

Old	New
Looks up interface by device + name	Uses Ironic port uuid as interface ID

IP Address Handling

Old	New
Assigns IP to any interface with ipv4_address	Only assigns BMC IP to iDRAC interface
Creates IP with parent prefix specified	Relies on Nautobot auto-assignment (no parent prefix)
Upgrades DHCP leases to permanent (type: dhcp → type: host)	No DHCP handling
Raises exception on IP/interface conflicts	Logs warning and continues

API Approach

Old	New
Uses GraphQL for rich queries (device + interfaces + cables + vlan_group in one call)	Uses REST API calls

Additional Features in New Implementation

• Handles interface name conflicts (deletes conflicting interface before update)
• Maps Ironic provision_state to Nautobot status via ProvisionStateMapper
• Syncs tenant from Ironic lessee field
• Supports custom_fields on device
• Event handlers for various Ironic events (provision, CRUD, power, maintenance)
• Delete device handler

[cardoe]

Can you describe the changes in the body of the PR?

[stevekeay]

I like this, but I have some concerns that if we get a "partial" update, we would overwrite some nautobot data but potentially leave behind stale records or attributes. Like for instance, we don't seem to delete any old interfaces or cables.

I think we should get this merged. I have left a boatload of style suggestions.

[stevekeay]

Just to be clear, I approved this because I think it will work, but we should still make the changes!