tampler commented on issue #8349: URL: https://github.com/apache/cloudstack/issues/8349#issuecomment-1855760597
@rajujith This issue boils down to the use case of ACS. 1. Modern large scale deployments won't allow ACS to be a front facing infrastructure unit. ACS will be hidden behind hardware (NetScaler, F5, Nicara) or software Edge/Application load balancers. 2. IPv4 is a scarce resource and its price only keeps growing. It's expensive to get a formidable range here in Russia and virtually impossible to buy own. 3. In my case, I have ALB in front of ACS and use a subdomain routing to access it, e.g `acs.example.com/ui -> cloudstack.ip.local:8080/client` 4. In my case, I have ALB in front of ACS and use RFC 1918 for all ACS ranges, including `public`. That's why `CPVM` link looks like this: `http://192.168.1.21/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=oW2Df...` which can't connect to an application VM in a `vpc subnet` My network map looks like below. I imaging similar setup to be used in most modern deployments with limited IPv4 range, server and cloud resources  -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
