make it easier to change http proxy details


Today in order to change proxy we need to reinstall/upgrade DCOS - because proxy settings are in config.yaml

The problem is that sometimes proxy requires authentication (username/password) and passwords can expire. Which means that we have to upgrade/reinstall DCOS whenever password expires, which is not ideal.

It would be great if there was some easier way to change http proxy details.

This was partially discussed with Karl at networking Slack channel and he suggested to create JIRA ticket.


Cody Maloney
October 27, 2016, 11:30 PM

Could maybe make it so you have two options in configuring this:
1. Everything owned by DC/OS (how it is today). That makes it so things like AWS Advanced Templates are configurable / usable / deployable
2. DC/OS makes the proxy env file in `/opt/mesosphere` a symlink to a file in `/etc` which the user controls (And then another flag to determine whether or not we should write that file on first cluster deploy)

Karl Isenberg
October 27, 2016, 11:34 PM

If the env file gets updated will things automatically pick it up or do you have to cycle a bunch of components to change it?

Cody Maloney
October 27, 2016, 11:48 PM

Completely untested! (We don't even have integration tests around basic proxy usage, let alone changing password proxy usage).

Borisa Zivkovic
October 28, 2016, 8:10 AM

there is no way DCOS could use OS http proxy settings?

Cody Maloney
October 28, 2016, 8:16 AM

As far as I'm aware there is no definitice standard of how to configure Linux software to use a proxy. Even if there is, multiple components in DC/OS require slightly different unique configuration formats themselves, and ensuring every DC/OS component properly reloads that config periodically is another layer of work /tasks


Jeremy Lingmann