engine: document and test impact of changing test helpers DNS names
Closed this issue · 6 comments
We probably need to change the domain names of the THs and I was asked to estimate the impact on probes.
I've done some investigation and reported my results on internal Slack channels.
I now need to test whether oohelperd.th.prod.ooni.io
is working as intended.
This conversation has led to some internal discussion and to #2704.
I wrote a diff that allows me to testing the new TH. Preliminary testing shows that the code is WAI for both Web Connectivity v0.4 and v0.5. Here are the related measurements:
-
https://explorer.ooni.org/m/20240410152440.960989_IT_webconnectivity_b0900e3e688def43
-
https://explorer.ooni.org/m/20240410152501.949255_IT_webconnectivity_defd3872b8c65b39
Here's an excerpt from my $HOME/.miniooni/engine/httpsdialer.state
:
// [...]
"oohelperd.th.prod.ooni.io:443": {
"Tactics": {
"18.192.17.176:443 sni=cdn.ketchjs.com verify=oohelperd.th.prod.ooni.io": {
"CountStarted": 2,
"CountTCPConnectError": 0,
"CountTCPConnectInterrupt": 0,
"CountTLSHandshakeError": 0,
"CountTLSHandshakeInterrupt": 0,
"CountTLSVerificationError": 0,
"CountSuccess": 2,
"HistoTCPConnectError": {},
"HistoTLSHandshakeError": {},
"HistoTLSVerificationError": {},
"LastUpdated": "2024-04-10T17:25:01.389858+02:00",
"Tactic": {
"Address": "18.192.17.176",
"InitialDelay": 0,
"Port": "443",
"SNI": "cdn.ketchjs.com",
"VerifyHostname": "oohelperd.th.prod.ooni.io"
}
}
}
}
// [...]
Now I am going to run this command:
export OONI_WEB_CONNECTIVITY_TH_URL=https://oohelperd.th.prod.ooni.io/
rm report.json
./miniooni web_connectivity 2>&1 | tee LOG.txt
Now I am going to repeat the above command with web_connectivity@v0.5
.
Alright, both runs have shown that we can use the new control servers. I think this issue is now complete.