weizhouapache opened a new pull request, #12484: URL: https://github.com/apache/cloudstack/pull/12484
### Description This PR includes the following changes on top of CloudStack 4.22.0.0 release: · Support VM deployment with keyboard "Spanish Latin American Keyboard". · Support additional VM details for Templates from OVA on VMware. · Support Spanish Latin American Keyboard in NoVNC console on VMware. Usage - Deploy VM with keyboard "Spanish Latin American Keyboard" In the instance deployment wizard, choose "Spanish Latin American Keyboard” as keyboard <img width="1056" height="785" alt="image" src="https://github.com/user-attachments/assets/30210dbe-c837-44c6-93af-f77e2459f75b"; /> - Support additional VM details for Templates from OVA If a VM template is registered with “Read Instance settings from OVA” set to true, users can add additional VM details beyond those loaded from the OVA file or created by CloudStack. These settings can be configured globally or per zone. (1)Enable Vmware additional details from OVA (it is disabled by default). <img width="1301" height="194" alt="image" src="https://github.com/user-attachments/assets/2e6ab281-37ac-409f-a743-35041002920a"; /> (2)To support the keyboard settings, set the value of global setting “vmware.allowed.additional.details.from.ova” “ to “keyboard” <img width="1299" height="218" alt="image" src="https://github.com/user-attachments/assets/03010613-85de-47a5-a6e2-a8cab8974da9"; /> When VM is Stopped, users can add, update or remove settings for keyboard. <img width="740" height="605" alt="image" src="https://github.com/user-attachments/assets/aa4486cd-cafb-4fc1-95dc-1e0989c6b438"; /> If the keyboard is “Spanish Latin American” inside Guest VMs, please set the keyboard to “es-latam”. - Support Spanish Latin American Keyboard in NoVNC console When user inputs the letters (upper cases and lower cases), numbers, and a list of special characters and keyboard combinations (provided by ARSAT), the correct characters should be displayed on the screen (Windows, or shell). Please refer to https://commons.wikimedia.org/wiki/File:KB_Latin_American.svg <!--- Describe your changes in DETAIL - And how has behaviour functionally changed. --> <!-- For new features, provide link to FS, dev ML discussion etc. --> <!-- In case of bug fix, the expected and actual behaviours, steps to reproduce. --> <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be closed when this PR gets merged --> <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" --> <!-- Fixes: # --> <!--- ******************************************************************************* --> <!--- NOTE: AUTOMATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE DOCUMENTATION. --> <!--- PLEASE PUT AN 'X' in only **ONE** box --> <!--- ******************************************************************************* --> ### 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? <!-- Please describe in detail how you tested your changes. --> <!-- Include details of your testing environment, and the tests you ran to --> #### 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]
