deploy probe-services v2 in production

[ainghazal]

The openvpn experiment depends on the newer endpoint we deployed a few months ago in the staging backend. To be able to test the release candidates, we need to deploy the service in production.

[hellais]

For an MVP can we just hardcode some endpoints in the test that we know are going to be stable? I don't think it's realistic to assume probe services v2 will be in production by the rollout of the experiment.

[ainghazal]

• there were a couple openvpn endpoints hardcoded; they were removed to ensure API can control switching off the experiment by delivering an empty list (possibly by country);
• it's possible to re-add those default endpoints
• the credentials problem remains unsolved; we cannot hardcode them in a production client (since they will expire); that was the reason that drove the VPN endpoint in the first place.

[ainghazal]

fwiw, the experimental card simply does not run the OpenVPN experiment if the API returns an error. So perhaps it's feasible to ship it and just enable the service whenever it's possible.

[hellais]

We are going to consider this done once we have the orchestra (/login, /register and /update) deployed in production. For the moment we are not going to do this for the openvpn endpoint since that's currently done via DNS and we should probably shoot for doing that using OONI Run v2.1