This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Feature-suggestion: "round-robin" probes
- Previous message (by thread): [atlas] Feature-suggestion: "round-robin" probes
- Next message (by thread): [atlas] Feature-suggestion: "round-robin" probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Sat May 5 11:58:11 CEST 2012
On 5/5/12 1:47 , Fred Baker wrote: > Well, a suggestion. > > Suppose that every time a probe does its test, it also reads<something> from RIPE that tells it the address of the target to probe next. This would allow RIPE (passing along your instructions, or executing its own) that could implement any of a variety of scenarios, and change them from time to time. > > That is already there. Probes are under full control of the Atlas infrastructure. The problem is more that the Atlas backend is very complex distributed system. So it takes time before the necessary datastructures and database tables are in place to really express the concept of looping over all probe.
- Previous message (by thread): [atlas] Feature-suggestion: "round-robin" probes
- Next message (by thread): [atlas] Feature-suggestion: "round-robin" probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]