Allow to set VncKeyboardLayout via REST API per VM, rather than a single global based config value. VDSM already accepted this as part of the API. GUI not covered by this. new VM API property: <xs:element name="keyboard_layout" type="xs:string" minOccurs="0" maxOccurs="1"/> commit b8f2c926daf2d3bcd4a9a5122987f6755566b805 Author: Martin Betak <mbetak> Date: Wed Jan 23 14:01:25 2013 +0100 restapi: Add per-VM VncKeyboardLayout Added keyboard_layout to display Change-Id: Ibdf2b9f74d483a1be9caaa6d6a47ba8de7c37420 Signed-off-by: Martin Betak <mbetak> commit 28cbf48ee9fd7117d141eebd155c8b22f8e4c888 Author: Martin Betak <mbetak> Date: Tue Jan 22 17:07:34 2013 +0100 engine: Add per-VM VncKeyboardLayout Added support for per-VM VncKeyboardLayout setting. Backend support for setting local values of keyboard layout per individual VM Change-Id: Ib73338ce279aa4f14f1332dbdebb1dd0f1cec974 Signed-off-by: Martin Betak <mbetak>
verified PUT === <vm> <display> <keyboard_layout>ar</keyboard_layout> </display> </vm> GET ===== <display> <type>vnc</type> <monitors>1</monitors> <allow_override>false</allow_override> <smartcard_enabled>false</smartcard_enabled> <keyboard_layout>ar</keyboard_layout> </display>
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0038.html