Virtualbox on Ubuntu 20.04

ansible-community / molecule-plugins

Collection on molecule plugins

MIT License

109 stars 73 forks source link

Virtualbox on Ubuntu 20.04 #61

Open jimbo8098 opened 3 years ago

jimbo8098 commented 3 years ago

Hi folks,

I've been setting up a CI pipeline for my company and Linux VMs have gone well so far. I suspect I will be fine with Windows too but I wanted to know the criteria for testing VMs on your plugin. I'm happy to raise PRs and so on. I have access to some pretty meaty hardware which means I can test different things if needed and I think I would have the support of my team if I did so.

My current environment is as follows:

Ubuntu 20.04
Virtualbox 6.1.18r142142
Vagrant 2.2.14
Molecule 3.2.3
Ansible 2.10.6
Python 3.6

I have my full setup documented (as a precursor to an ansible role further down the line) and can go into more detail if needed.

apatard commented 3 years ago

hi,

I'm not sure to understand. If you're talking of the list of systems supported written in the README.md, it's the list of things that can be tested by the CI, so we have confidence of it working (or not). It doesn't mean that other systems won't work, it's just it's not tested. As regards this exact setup, I'm not sure it's currently possible to reproduce it in the CI. The platforms are either from GitHub action or from Ansible Zuul.

GitHub action has 20.04 but there's no nested virtualization, that's why Virtualbox is tested on macosx.
For Ansible Zuul, I'm not sure 20.04 is supported and if it's the case, it will be with libvirt, since CI using Virtualbox is painful. I mean, Virtualbox needs to build and load an external kernel module in order to work, which is really complicated in CI environments (assuming it's possible to load an external module which may be not the case)

jimbo8098 commented 3 years ago

I've added my environmental information above because I know they work in my case although I can hardly say I'm using all the features of it. My intention is to fully test my environment so I can add it to that supported list and potentially add some testing to your actions.

I seem to remember having a lot of success running chef infrastructure tests on Travis CI btw, could be worth considering.

jimbo8098 commented 3 years ago

Would it be worthwhile simply adding a list of working configurations and some notes somewhere? I'd be happy to go into more detail on my setup.

apatard commented 2 years ago

Hi, I've opened a discussion regarding documentation https://github.com/ansible-community/molecule-vagrant/discussions/173. Some feedback about what may be added/modified in my doc update in order to close this bug would be nice. Thanks