Open critzo opened 9 years ago
Is this something that we need to do or you? I see that http://mlab-ns.appspot.com/ooni?policy=all does not return the tool_extra
key.
I am now going to implement https://trac.torproject.org/projects/tor/ticket/13812, but I would like to know if I should switch to using mlab-ns or continue for the moment using just testing.
I updated the bouncer and ran ooniprobe a couple of times with a standard deck to see if everything is working as expected and it seems to be the case.
The tests that are supported by mlab are reported to you, the ones that are not are sent to our collector!
@technosopher can elaborate, but yes, we need to merge code supporting ooni from mlab-ns-testing into mlab-ns. Once that's done, we'll need you to switch from testing to mlab-ns, but for now stick with testing.
Got it. Will the data that is collected to the nodes returned by the test mlab-ns be saved or will they be tossed?
I believe this issue can be closed at this point since ooni is pointing to mlab-ns (the production one).
Currently ooni points to mlab-ns-testing, because code specific updates to mlab-ns were prototyped there with the intent to merge up to mlab-ns. Once mlab-ns is updated, point ooni at mlab-ns.