weizhouapache commented on issue #3296: [master] noVNC Console Integration URL: https://github.com/apache/cloudstack/pull/3296#issuecomment-588328704 > @weizhouapache that's good to know. > > @DennisKonrad this PR is far from complete for general consumption, and possibly requires the following (and more): /cc @PaulAngus @davidjumani > > * Test and support XenServer, VMware in addition to KVM > * Support TLS/secured vnc connection when libvirtd is secured by CA-framework for KVM > * Validate the token exchange and security concerns (I've a bunch of test cases, plan in mind) > * Add support for active session management (allow only one view per VM), the active sessions reported by CPVM agent is used by the management server to add/remove more CPVMs in a zone > * I personally prefer a java-based websockets proxy http/https server which can work with ^^ and give us more control over connection validation and security (esp with the CA framework), we probably want to reduce additional packages/dependencies. I'm also not sure if/how could python/websockify provide a way to track active sessions and manage connection security. > * Support for multiple keyboards (like the current console proxy, for example jp, uk, us, fr etc) > * While Hyper-V largely does not working out of the box, but legacy console proxy proxies RDP (I think) on Hyper-V and therefore we also need to find suitable replacement for rdp-vnc cross-over, or if newer HyperV can support native VNC (needs checking @PaulAngus) > * Provide an upgrade path for users and discuss whether in the next release we want to deprecate and remove the current console proxy or simply remove in the next (unless all existing requirements of legacy console proxy are replaced and novnc is tested in various environments, it's not best to simply remove the legacy console proxy) @rhtyd good you have many nice ideas ! Maybe we can create a SIG for it.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
