[00:22] <tz_> further tinkering tells me that $cloud-config-url is pulled from DEFAULT_MAAS_URL in maas_local_settings.py .. How do I set that variable for different networks/interfaces in a cluster?
[00:32] <bigjools> DEFAULT_MAAS_URL is the address of the region and needs to be reachable from anywhere
[00:36] <tz_> so you're saying the cloud-config-url can only be one IP per cluster?
[00:47] <bigjools> it's the address of the app server
[00:48] <bigjools> it's one IP globally
[00:48] <bigjools> well not IP, a host
[00:48] <bigjools> URL to a host
[00:48] <bigjools> all maas networks need a routing to the region appserver
[00:49] <tz_> so say that host has multiple interfaces setup, how do I set default_maas_url to 0.0.0.0 or some sort of dynamic IP? is it possible at all?
[00:51] <bigjools> you need to set it to the IP of the interface that can route to and from the cluster networks
[00:51] <bigjools> s/interface/region's interface/
[00:52] <tz_> which can only be one at a time?
[00:52] <bigjools> the URL you set is handed to the nodes when they're deploying so they know how to contact the region
[00:52] <bigjools> yes, one
[00:52] <bigjools> on big deployments with many appservers it is likely to be a load balancer
[00:53] <tz_> this is just one server, that's why it has multiple interfaces/vlans
[00:54] <tz_> its would be a waste to start throwing in extra cluster controllers and load balancers, hence why I want that one variable to work for the networks setup on the one cluster
[00:55] <bigjools> you just need a route from the cluster interfaces to the relevant region interface
[00:55] <bigjools> then it will work
[00:57] <tz_> yeah i get that, trying to keep the networks segregated without adding a bunch of static routes and cross-vlans
[00:58] <tz_> in the config file it has a comment "
[00:59] <tz_> "configuration can, and probably should, override this."  .. do you know what config it's referring to?
[01:01] <bigjools> maas_local_settings
[01:02] <bigjools> it's set from dpkg-reconfigure