The MAAS 2.0 documentation clarifies the following:
Note: Despite the web interface labelling the external proxy field 'Proxy for APT and HTTP/HTTPS', the proxy is only for APT and not for HTTP/HTTPS as implied.
So if I wanted to have my MAAS region controller node to act as the HTTP/HTTPS proxy for all the cloud nodes, how do I change the Squid configuration to take on the HTTP/HTTPS proxy role (as well as the APT traffic - I assume Squid is the APT proxy).
In my configuration, my region controller has the first NIC connected to the office WAN modem/router, and the next NIC connected to a managed switch that all the other nodes are connected to. The region controller is the only machine with a direct line to the internet. All MAAS nodes can update, upgrade, and install APT packages, but Juju can't spin up LXD containers because they can't resolve the images from the linuxcontainers.org .
Additional context: I was testing out the setup tutorialized at http://blog.naydenov.net/2015/11/deploying-openstack-on-maas-1-9-with-juju-network-setup/ which describes a configuration with all the VLANs and subnets set up before install. Unfortunately, I'm having a hard time getting Squid to let the maas-management
subnet out.