ansible-community / ansible-community/molecule-plugins
Molecule + Vagrant using remote libvirt server
- Dominant language
- Python
- Stars
- 164
- Forks
- 113
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 1
Description
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 ](https://github.com/ansible-community/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://` 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.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the old molecule-libvirt documentation, especially the libvirt_host and libvirt_user options, then inspect the current Vagrant/libvirt configuration path. Reproduce the qemu:///system timeout with a qemu+tcp:// configuration. Done means determining whether remote connections are supported and identifying the required documentation or implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- infrastructure, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100