Question: running commands on multiple instances about molecule

[retr0h]

Furthermore, defining multiple instances to test a role on different platforms is not an intended Molecule's usage pattern?

I now remember why we took this approach. When we wrote molecule, we were solving a use case specific to us. We wanted the ability to perform multi-node testing. Kitchen didn't support this, however, it did support multi-platform. We implemented multi-host on a single platform. Once we decided to implement multi-platform, it was implemented against a single-platform at a time. I'm working on a rewrite of molecules config, which will likely address this in the future. However, thats a couple months away from landing.

[identifystation]

@tjanez At the moment we don't have a mechanism to do multiple platforms in a single converge. The entire thing is built around the idea that you're converging one or multiple instances of the same platform. For our needs, we do these as separate steps, though I could definitely see how it would be convenient to test multiple platforms in a single shot.

[tjanez]

@abrown-sg, thanks for your explanation.

So, if I understand current Molecule's design correctly, instances are meant to be used to test how a role behaves under different configurations/states of the currently chosen platform?
Furthermore, defining multiple instances to test a role on different platforms is not an intended Molecule's usage pattern?

[butla]

@retr0h Hey, so is there any progress on that?

FYI my current case (maybe I'll change this up) looks like this:

• one Ansible role that's supposed to work on many OSes
• I'm using Vagrant as the driver
• CentOS7 should use virtualbox provider
• Ubuntu 16 should use the lxc provider

[retr0h]

Molecule v2 supports scenarios. Your scenarios can be written for each distro and driver.

[butla]

@retr0h Thanks!