feat(devnet-8): show inventory hostnames in the bootnodoor web UI

[barnabasbusa]

Enables the new bootnodoor_ip_names_enabled toggle for devnet-8's bootnodes. The bootnodoor role uploads the devnet's inventory.ini to each bootnode and passes --ip-names to the container, so the bootnodoor web UI shows inventory hostnames (e.g. bootnode-1, grandine-besu-2) instead of bare IPs in its node tables — the real IP:port stays available as a hover tooltip.

Since bootnodoor re-reads the file on change, re-running the playbook after inventory updates refreshes the names without restarting the container.

Merge order

1. feat(webui): sortable columns, status filters, and stable row heights on node tables bootnodoor#53 + feat(webui): map IPs to operator-defined display names via --ip-names bootnodoor#54 (adds --ip-names; wait for the master image rebuild)
2. feat(bootnodoor): optionally upload an IP->name mapping for the web UI ansible-collection-general#578 (role support — this repo tracks the collection's git master)
3. this PR

Merging this first would fail the bootnodoor container on the unknown --ip-names flag.

[redpandabot]

Summary

Enables bootnodoor_ip_names_enabled for devnet-8 so the bootnodoor web UI shows inventory hostnames instead of bare IPs. The change is a one-line toggle; I confirmed the upstream support it depends on (collection role var + bootnodoor's --ip-names) is absent from both current masters and arrives via git-master tracking, consistent with the author's documented merge order. One deployment-sequencing hazard is worth a look.

Issues

• 🟡 ansible/inventories/devnet-8/group_vars/bootnode.yaml:63 — Toggle auto-activates via git-master tracking before the bootnode hosts have a rebuilt bootnodoor image — This repo tracks the collection and the bootnodoor image from git master (requirements.yaml:22-23, bootnode.yaml:47), and today both are inert: the collection role at master f472dcc has no bootnodoor_ip_names_enabled, and the bootnodoor app at master feat(el): ENR bootnodes and discv5-only, staged for devnet-8 #52 has no --ip-names (collection #578 / app devnet-7: drop the stale powfaucet_agents image pin #53+devnet-7: deploy the agent PoW faucet + fix browser faucet gas limit #54 are not in the cross-repo checkouts, so I could not verify those changes). The merge-order note sequences merges, but once collection #578 lands, the next devnet-8 bootnode playbook run passes --ip-names automatically regardless of host state; the role's docker_container task sets no pull and devnet-8's watchtower list excludes bootnodoor, so nothing in the playbook refreshes the container image. A run that happens after #578 merges but before the hosts get the devnet-7: drop the stale powfaucet_agents image pin #53+devnet-7: deploy the agent PoW faucet + fix browser faucet gas limit #54 image fails the container on the unknown flag. If the deploy flow pulls/updates the bootnodoor image before every run (I could not trace it from this repo) this is a non-issue.

---

_{Reviewed @ 82b340ef
Red pandas make a twittering "huff-quack" — the original microblogging.}