I was able to solve it, actually, up to the point where you have a readily available template with cloud-init ready to read the user-data. Just to give you a head start :)
"boot_command": [
"<esc><enter><f6><esc><wait> ",
"<bs><bs><bs><bs><bs>",
"ip={{ user `vm_ip` }}::{{ user `vm_gateway` }}:{{ user `vm_netmask` }}::::{{ user `vm_dns` }} ",
"autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/ ",
"--- <enter>"
]
This configures autoinstall, which can run cloud-init commands. And will run cloud-init anyway.
These are the variables:
I was able to solve it, actually, up to the point where you have a readily available template with cloud-init ready to read the user-data. Just to give you a head start :)
This configures autoinstall, which can run cloud-init commands. And will run cloud-init anyway.
These are the variables:
Then you can reset cloud-init through ansible (run by packer), for example.
If you want to write an updated article, I'll be happy to help, if you think you need any, of course!