My nodes can access the Internet perfectly well, which demonstrates that your problem is entirely dependent on each kind of network set up.
This is partly why there is a proxy setting on the region controller, but this is not used after the node is installed.
So I think MAAS can do better in a couple of ways:
1. Set up the proxy on installed nodes if it's set on the region's settings
2. Allow admins to configure ip forwarding on the region controller
However #2 is problematic because the region controller is not really a single machine on scaled-out installation, there could be many appservers and Postgres slaves.
How do you think MAAS could help in that scenario where the region is not a single machine?
Hi Jeff,
My nodes can access the Internet perfectly well, which demonstrates that your problem is entirely dependent on each kind of network set up.
This is partly why there is a proxy setting on the region controller, but this is not used after the node is installed.
So I think MAAS can do better in a couple of ways:
1. Set up the proxy on installed nodes if it's set on the region's settings
2. Allow admins to configure ip forwarding on the region controller
However #2 is problematic because the region controller is not really a single machine on scaled-out installation, there could be many appservers and Postgres slaves.
How do you think MAAS could help in that scenario where the region is not a single machine?
Cheers.