That's the thing: people don't put their HPC clusters on the public Internet; so an internal IPv4 network just keeps being fine.

True, but on the other hand it might be that all private use blocks are already in use (10.0.0.0/8 is totally in use in our internal LAN), so if I want the nodes to reach those private IPs, I can't assign the same block. And we do have services on IPv6.

Perhaps you have not seen some of the other solutions out there in this space.

Warewulf _is_ the simpler solution.

We're always looking towards IPv6 support! And you _can_ do it today, with a little bit of work. But it's been difficult to prioritize in the main project when so few of our users (read: maybe one) have expressed interest.

> when so few of our users

existing users, I suppose. New users are looking for exactly this feature and will walk away. So, you can now count it up to 3.

IPv4 has gotten quite expensive. A newer company I'm working with doesn't even have IPv4 access past the edge. There is just a little proxy that handles IPv4 translation on the edge; it barely gets any traffic.

It's PXE boot for mostly stateless node / disk images, with a template-based overlay system for customizing the image as it's applied to the node.

So with the overlay you can make node-specific changes? I was reading through the initial setup guide but I couldn't figure out how you actually specify which node gets which overlays (or one-off edits of whatever kind).