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] Running RIPE probe VM
- Previous message (by thread): [atlas] Running RIPE probe VM
- Next message (by thread): [atlas] New on RIPE Labs: RIPE Atlas on the Go
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tom Glass
me at tom.glass
Tue Nov 14 17:16:02 CET 2017
**wouldn't be happy Sent from Blue On 14 Nov 2017, 16:15, at 16:15, Tom Glass <me at tom.glass> wrote: >Hello, > >Atlas did a good review on this >https://labs.ripe.net/Members/suzanne_taylor_muzzin/exploring-the-idea-of-ripe-atlas-virtual-probes > >I agree virtual probes save costs but there is other risks as >highlighted, you can in theory convert the software on the probe to a >VM however it would likely involve dismantling the probe and I'm pretty >sure RIPE Atlas would be happy. For each virtual probe you would need a >physical so pretty pointless. > >Luckily they don't use a lot of power or space and easily fit in racks, >cupboards or even down the back of your sofa depending on where your >router is. > >Anyway hope this helps. > >Regards, >Tom > >Sent from Blue > >On 14 Nov 2017, 16:07, at 16:07, Evgeniy Sudyr <eject.in.ua at gmail.com> >wrote: >>Hello All, >> >>I'm interesting for running RIPE probe on VM or Docker container. Any >>chance to get this idea real? >> >>-- >>With regards, >>Eugene Sudyr -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20171114/ca80200d/attachment.html>
- Previous message (by thread): [atlas] Running RIPE probe VM
- Next message (by thread): [atlas] New on RIPE Labs: RIPE Atlas on the Go
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]