On Mon, Dec 17, 2018 at 01:36:57PM +0000, secli...@boxdan.com wrote: > On Mon, Dec 17, 2018 at 10:22:56AM -0200, Daniel Bolgheroni wrote: > > Maybe ansible is not the answer here. > > You are probably correct. Do you know a better way?
If you're going to run on some public cloud, they usually offer the possibility of keeping a custom image you provide, and use this image to deploy new VMs based on it. You can do a normal install and customize it adding the python package (you do not need ansible on the target machine, just python) and your public ssh key for the user ansible will use to connect. This customization can be done manually or using siteXX.tgz and install.site that OpenBSD provides: https://www.openbsd.org/faq/faq4.html#site >From here you should be able to point ansible from the control machine to the target VM, and run your playbook to further customize your installation. Of course that, at this point, the network should be already up. This depends on your public cloud, but usually a 'dhcp' inside your hostname.if(5) will do. But note again this is not a fully-automated installation using ansible, which isn't trivial on any OS. But it helps a lot. -- db