nvazquez opened a new pull request, #11019: URL: https://github.com/apache/cloudstack/pull/11019
### Description This PR extends the VMware to KVM Migration tool by displaying the `virt-v2v` and `ovftool` versions (when available) on the UI and storing them as host details. <img width="951" alt="Screenshot 2025-06-12 at 16 38 57" src="https://github.com/user-attachments/assets/a9ac4a40-c987-430c-bc85-45657648863e"; /> ### Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [ ] Bug fix (non-breaking change which fixes an issue) - [x] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) - [ ] build/CI - [ ] test (unit or integration test code) ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [ ] Major - [ ] Minor #### Bug Severity - [ ] BLOCKER - [ ] Critical - [ ] Major - [ ] Minor - [ ] Trivial ### Screenshots (if appropriate): ### How Has This Been Tested? Tested on KVM env with 2 Ubuntu 24.04 hosts: - Installed virt-v2v in one host -> Verified only virt-v2v version is listed when selecting a host for migration - Installed ovftool on the same host -> Verify also ovftool is displayed when selecting a host for migration #### How did you try to break this feature and the system with this change? <!-- see how your change affects other areas of the code, etc. --> <!-- Please read the [CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md) document --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
