> Cool! We're actually in the process of overhauling consoles for VM Portal. > We currently have Windows RDP in the Admin Portal, and we are actively > working on it for VM Portal. Here are some screens from the design: > > We also have SPICE (thick client) fully implemented in both portals, thick > client VNC in both portals, novnc (web-based) in Admin, and novnc coming > very soon in VM Portal (4.3.2 at the latest, but I hope 4.3.1) as part of > the overhaul. > > Also, would you mind please reviewing the designs we have so far? I'm > interested in others' opinions, especially someone who has already been > thinking about this.
That's awesome to hear! We were wondering why novnc was an Admin only feature and why 'Console' in VM Portal felt sparse. Looking at these designs, this is kinda what I was going to go for anywho haha, with support for other RDP solutions. > Is Mechdyne TGX much different than Windows RDP, SPICE, and VNC? If so, > what is the use case for using that over Windows RDP / SPICE / VNC? Mechdyne TGX is an TDP solution that offers significantly higher frame rates (60+ frames per second) and resolution (We can hit 4k resolution); to our understanding, Windows RDP and SPICE cannot hit those numbers. For the average workstation user, SPICE is sufficient! We have some users that are heavily invested in simulation and potentially VR, so a close recreation in terms of frame rate and resolution is needed and Mechdyne TGX supports this. You can read more about this here: https://tgxremotedesktop.com/tgx-features/ I guess this leads into my next question... Is it possible to configure how console.rdp is created in VM Portal or achieve parity between how it's created in VM Portal and Admin Portal? When you open up the console.rdp file created in Admin portal, under where "full address:s:", the IPv4 address is listed. However, when you open the console.rdp file created in VM Portal, under where "full address:s", it takes the VM name instead of something like the IPv4 address or even the FQDN of the VM. Currently, someone wrote a bash script to grep out the "full address:s" value and use it alongside TGX, but this doesn't work on the VM Portal due to the value being set to the VM Name. The workaround is to register the VM name in our DNS so that it will resolve with an IPv4 address, but I feel that this is a poor solution. My suggestion is for the console.rdp generated in VM Portal, instead of using the VM Name, use either the FQDN or the IPv4 address. I can see the counterargument that this will expose the FQDN/IP address to the user. > And I would certainly love for you to help test it out as we're nearing > completion, at the least. If you want to code, we would love to have you :) I'd love to help! Problem is, I guess I'm trying to start from 0 and I'm not sure HOW to start developing for web-ui or even WebAdmin. How would you suggest setting up? Let me know if you have any further questions and thank you for taking the time to respond! _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/FCZMWR4ODZJ7P6IMTHJ7NPPX7KGWDIMT/
