This message was deleted.

Hey Ulf, I think creating the VMs with unique tags and then calling the Harvester API after Terraform has finished is a good strategy to go about this. I'm not sure it will always be viable to let Terraform output these information, since it can take some time after Terraform resources are created until the information is populated.

DHCP should die. Would really love to see more advanced capabilities around using static IPs pulled from an IPAM solution. I have been automating infrastructure and applications on top of that infrastructure for ten years now (Starting with Cisco CloudCenter and was on the Tiger Team there) and it has always been a requirement to get IPs from an IPAM database and assign it directly to a VM. With all the engagements I have done over these past years only two have actually used DHCP. And it was always a trainwreck. Especially when you build in DNS record management as well. You guys are really close to having the functionality there, just not quite there. For example, I have the ability to provide a cloud-init Network configuration, but it is completely inflexible. Would be nice if we could define IP Pools and then be able to specify the IPPool when we are deploying a cluster using the Harvester provider.

@cuddly-restaurant-47972, I know the pain DHCP can cause. But sometimes it's all that's available for Harvester to use. If you feel that Harvester is lacking something, the best way to get things moving is to have a feature request with a clear description of what that is. I'd greatly appreciate it if you could put in the time and effort to write one for the functionality that you're missing from the cloud-init network configuration.

I will try and come up with some user stories and see if that can help give some context around how things would ideally work on the new DDI guidelines.