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/[email protected]/
[atlas] Automating software probe creation?
- Previous message (by thread): [atlas] Automating software probe creation?
- Next message (by thread): [atlas] Automating software probe creation?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Mon Jan 4 11:53:06 CET 2021
On 2021/01/02 8:25 , Steve Gibbard wrote: > As far as I can tell from the documentation, it looks like the probes are identified by the encryption keys in /var/atlas-probe/etc/probe-key* . If creating new probes from an image, is it sufficient to make each probe generate its own encryption keys, or are there other files that need to change? If you build the debian package, then you can install that as many times as you like. Probes are indeed identified by their public keys. > For registering the probes, I see a web form that requires being logged into a RIPE account, and don’t see any equivalent in the API documentation. Is there a way to register new software probes via the API? We are working on an API. However, the only thing the API will do is to copy the public key to the atlas backend systems. You still have go to the web size, log in, etc. We want to associate a user with each probe. Philip
- Previous message (by thread): [atlas] Automating software probe creation?
- Next message (by thread): [atlas] Automating software probe creation?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]