shwstppr commented on issue #8412: URL: https://github.com/apache/cloudstack/issues/8412#issuecomment-1876592000
Did some investigation for this. Guest OS and VM import issue should be solved with #8426 (currently it needs #8429 to be merged). The hypervisor capabilities issue is more complex and below are my findings, - Currently, the code will use the capabilities of the parent version if the capabilities of the minor/patch hypervisor version are missing. - In the above case there is no option to update the capabilities manually using updateHypervisorCapabilities API as there is no entry for the given hypervisor version, eg: VMware 8.0.0.2 Based on the above findings and the original report do we need to consider the hypervisor capabilities issue as a blocker? To solve this hypervisor capabilities behaviour I feel the following are our options: 1. Use the mechanism of retrieving hypervisor capabilities from the parent hypervisor version only for patch or lower versions. Add logs in the code to highlight parent version capabilities are used. Document the behaviour. 2. Use the mechanism of retrieving hypervisor capabilities from the parent hypervisor version as it is with additional logs. Support manually updating capabilities for inexisting minor or lower hypervisor versions by adding `hypervisorversion` param in the `updateHypervisorCapabilities` API. 3. Revert this mechanism of retrieving hypervisor capabilities from the parent hypervisor version and add capabilities for 8.0.0.2 in the traditional manner. @andrijapanicsb @weizhouapache cc @harikrishna-patnala @DaanHoogland @nvazquez feedback, suggestions? -- 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]
