molecule-kubevirt goes to 0.1.0: could it move to official driver repo ?

[jseguillon]

Hi all,
I'm proud to announce I finally reached the point the KubeVirt driver for molecule is now good enough to be declared as a first stable release. Tag 0.1.0 is ongoing:

• any VirtualMachine defaults can be supercharged, including cloud-init, disks, networks, etc.. Rules are documented in README,
• most of the code is tested: many via creating non started VMs and comparing spec to tracked yamls in source
• default cloud-init image points to latest KubeVirt fedora build (= driver is no more responsible for providing default image),
• molecule can now run both from inside or outside Kubernetes
• no more collection dependency (removed deprecated kubevirt collection)

I'd love to transfer this driver to official community. Would you welcome it ?

[ssbarnea]

Sure! Initiate a transfer to ansible-community and if it does not allow you to do so, do it towards me, ssbarnea and I will do it myself.

[jseguillon]

Great !

I will fix one known bug, tag 0.1.0 and then do the transfer.

[jseguillon]

Hi @ssbarnea I just transferred molecule-kubevirt.

[ssbarnea]

Do not forget to add ssbarnea and ansible-community users of pypi, so we can publish or yank stuff (hopefully never).

[jseguillon]

Just done.
Alas, tox workflow is now red status. I'm looking at it but as usual, settings pipelines back to green may take some time :/

[ssbarnea]

FYI, In about one week or so, I am going to work on #3555 -- which should ease the driver maintenance a lot as we will have an unified CI pipeline.