Closed kinvaris closed 8 years ago
For Fargo it should be able to install without having KVM installed as you can connect with the edge. Just checking for the depenency and blocking is not the way to go, You should be able to extend a vPool even if KVM or VMware isn't there.
For Fargo, this is - to my knowledge - not the case Creating a vPool will not work even when using Edge I cannot remember reviewing anything from @khenderick which allowed this
Correct, at this moment KVM or VMWare is a requirement, and we never got a request to change this so a vpool could be extended to a non-hypervisor backed node. There were a few tickets in the past for allowing non-hypervisor backed nodes, but these were postponed.
It also seems that @kvanhijf did add a check that raises a more informative error when virsh is not installed in Fargo.
Any idea why we decided to ask for the hypervisor type in the OVS setup step? Could we remove that step and on a vpool extend check for the hypervisor? If we detect KVM (or should we ask) the user, we could use the code path which uses virsh. I'm aware this doesn't solve the issue for the Edge.
Because back then every StorageRouter had to be on a Hypervisor, either (bare metal on) KVM or (VSA on) VMWare. What you suggest could indeed be part of the "remove hypervisor requirement" storycard implementation.
And the report itself (the thing @kinvaris mentions) is already fixed in Fargo.
Edit: well, not perfectly fixed, a nicer error is raised, but it's not covered before the wizard finishes, which would be better.
vPool succesfully created
Test passed. Could not reproduce the issue specified in this ticket. If a similar error occurs once more, we should create a more general ticket as this one only handles one issue (qemu-dependency)
When trying to create a vpool, it failed because the KVM dependency is not checked: