Erik, It will take around month or 2 months to hit code base.
For testing purposes I will go with quickcloud. It will be easier to test that way as you can run CPVM functionality on you management server without deploying CPVM. It will save you a lot of pain. https://cwiki.apache.org/confluence/display/CLOUDSTACK/QuickCloud Regards, Anshul On 23-Jun-2015, at 4:53 pm, Erik Weber <terbol...@gmail.com> wrote: Hi Anshul, Thank you for the update. Do you have a rough estimate for when this refactor might hit the codebase? I don't expect my changes to hit 4.6 due to time constraints anyway, so if your changes are around the corner I might as well wait. Do you happen to know what the easiest way to redeploy systemvm.iso for testing purposes is? Intended hypervisor is XenServer, but if it is easier with KVM I'm open to switching. Regards, Erik On Tue, Jun 23, 2015 at 1:17 PM, Anshul Gangwar <anshul.gang...@citrix.com> wrote: Hi Erik, I will be working on console keyboard support refactoring. The main purpose of this refactoring will be to enable end user to add their own keyboard mappings without need to know CloudStack code much. As of now all keyboard mappings are either into ajaxkeys.js or ajaxviewer.js. These files goes into CPVM through systemvm.iso. Regards, Anshul On 23-Jun-2015, at 3:54 pm, Erik Weber <terbol...@gmail.com<mailto: terbol...@gmail.com>> wrote: Hi, I am guessing there are more than me that's having trouble with keyboard with non-us layouts. I'd like to improve it, atleast for my native charset. Has anyone done something like this, and have some insight into the process? I've found this [1], that to some degree explain the process. If I'm testing locally, what are the steps required to update the files? Do they rely on the mgmt server or the console proxy? If the latter, how do I update it (if not manually)? If anyone wanna co-work on fixing Norwegian charset, let me know :-) [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Non-US+Keyboard+Support+for+Console+Proxy -- Erik
