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] decommission of virtual probes
- Previous message (by thread): [atlas] Customs value of Atlas Probe
- Next message (by thread): [atlas] decommission of virtual probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ripe.net at toppas.net
ripe.net at toppas.net
Mon Nov 6 20:53:14 CET 2023
Hello folks, dear Atlas team, I would like to discuss the case, where a virtual probe is decommissioned because the place where you ran it will no longer be available. For example, a VPS which you have rented somewhere, but you've decided to cancel that service. Does it make sense to create and keep a backup of the virtual probe, so that you can re-deploy it later (with another AS)? Or is it better to delete the virtual probe and create a new one? Also: is there an official way to decommission a virtual probe permanently? I felt like this could be interesting for other people too, so i decided to discuss this question publicly. BR, Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20231106/71b2720e/attachment.html>
- Previous message (by thread): [atlas] Customs value of Atlas Probe
- Next message (by thread): [atlas] decommission of virtual probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]