Console issues in a distributed environment over NAT

Hi all, i'm trying to deploy oVirt to manage multiple 'data centers' (really just very basic deployments of single hosts using local storage that are deployed in varying geographic locations), where each host/resource pool is (unfortunately) only accessible via NAT. I've setup port-forwards for all functions, including SPICE/VNC, but am running into issues with the 'console' button in the GUI. When I initially added the host I added it using the NAT IP, however when trying to connect to console the console.vv file generated from the GUI references the local (private) IP of the host, instead of the NAT IP of the upstream firewall - so I have to manually open the file to change it to the NAT IP in order to connect to a VM's console. This is a minor annoyance for me, but it does ultimately the tool will be used by others who are less comfortable with steps like these. Is there a way around this, to have the console.vv generate with the IP oVirt is using to connect to the host, instead of its discovered local IP? Also if you can think of any other concerns I may encounter in a NAT deployment like this, please share! Thanks!
participants (1)
-
shailigum@gmail.com