I am trying to use a remote server configured with Libvirt to run molecule tests on/against. I have configured Libvirt to listen on a TCP port which is accessible from my workstation.
I am working on a M1 Macbook so testing roles with Molecule against a wide variaty of operating systems is a major hassle.
So I started looking into Molecule with Vagrant and Libvirt as a driver. When looking at the old molecule-libvirt documentation, it mentions connection options like libvirt_host and libvirt_user: remote host parameters. libvirt_user should belongs to libvirt group..
But whatever I provide as configuration and no matter where I place this, it never seems to do a remote connection. Molecule always times out on qemu:///system even though the configuration parameter I provide is qemu+tcp://<ip> and various inputs like this.
Am I misreading the documentation or has the code-base been altered when it merged and has this feature been removed?
I am trying to use a remote server configured with Libvirt to run molecule tests on/against. I have configured Libvirt to listen on a TCP port which is accessible from my workstation.
I am working on a M1 Macbook so testing roles with Molecule against a wide variaty of operating systems is a major hassle. So I started looking into Molecule with Vagrant and Libvirt as a driver. When looking at the old molecule-libvirt documentation, it mentions connection options like
libvirt_host and libvirt_user: remote host parameters. libvirt_user should belongs to libvirt group..But whatever I provide as configuration and no matter where I place this, it never seems to do a remote connection. Molecule always times out on
qemu:///systemeven though the configuration parameter I provide isqemu+tcp://<ip>and various inputs like this.Am I misreading the documentation or has the code-base been altered when it merged and has this feature been removed?
Thanks in advance.