You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of a question than a proposal about if it would make sense to use virt-lightning as backend for implementing molecule-libvirt.
If this would ease implementation it would be a serious pro. My only concern is that molecule is also a multi-platform development tool that is supposed to be able to use remoting support, in that case remoting support of libvirt.
In case it was not clear, remoting support is what enables such a cli tool to run on platforms that do not support the backend, like MacOS or Windows.
AFAIK remoting is not yet supported by virt-lightning, but if this is planned and achievable we are good.
Feel free to look at ansible-community/molecule-libvirt#13 and join the effort. At this moment there is only a driver skeleton there, with CI enabled that has libvirt installed, making very easy to add the missing create/destoy pieces.
The text was updated successfully, but these errors were encountered:
This is more of a question than a proposal about if it would make sense to use virt-lightning as backend for implementing molecule-libvirt.
If this would ease implementation it would be a serious pro. My only concern is that molecule is also a multi-platform development tool that is supposed to be able to use remoting support, in that case remoting support of libvirt.
In case it was not clear, remoting support is what enables such a cli tool to run on platforms that do not support the backend, like MacOS or Windows.
AFAIK remoting is not yet supported by virt-lightning, but if this is planned and achievable we are good.
Feel free to look at ansible-community/molecule-libvirt#13 and join the effort. At this moment there is only a driver skeleton there, with CI enabled that has libvirt installed, making very easy to add the missing create/destoy pieces.
The text was updated successfully, but these errors were encountered: