My experience using this tool (problems and proposals)

[fperillo]

Today I was finally able to have my first ubuntu 22.04 VM built with this tool and I'd like to list the problems I had. NOTE: I should have read the official manual with more attention and give blogs less importance. I know that almost all problems are not due to this tool

1. Git: spent a lot of time without creating the repository and packer failed. Created the repository, packer started.

2. DHCP: probably I did not pay attention, but I didn't read about DHCP as a pre-requisite, and I don't have a DHCP server anyway. I may create one on a "build" VLAN. I had to add the ip definitions in boot_command, so the installation process could start.

3. Internet connection: at least for ubuntu, I was not able to set a proxy. cloud-init reads the configuration and Curtis starts but requires internet. Tried several proxy configurations but none worked. Had to open the firewall. I didn't understand if Curtis is installing from internet or CD-ROM

4. mkpasswd... where are you? in whois package...

5. ansible failed to gather facts. Using -debug when packer asked how to continue, I investigated the authorized_hosts... but it is not using keys in that step, just password. And I later realized that my opens was > 9... Added the line in ansible.cfg

6. ansible run but build failed since packer was not able to eject the CD-ROM.... it was able to mount the iso but not to eject it? Ok, I did not create the sphere user, a quick check, and a permission was missing. Assigned, build completed

Evviva !!!

I started the new VM and found that the IP address was deleted and probably the VM was waiting for DHCP.

Now the proposal:

• A string variable set in private config dir to be added to boot_command, so to not modify the build tempate

• A little script to check pre-requisites: are we in a git repository ? is openssh version > 9 and the parameter in ansbile.cfg is missing? Are you connected to internet? Is a DHCP server available?

Thank you