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] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)
- Previous message (by thread): [atlas] VM probes
- Next message (by thread): [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Pavel Odintsov
pavel.odintsov at gmail.com
Mon Nov 9 13:54:15 CET 2015
Hello, Robert! I completely agree with you. I'm thinking from developer point of view. I want to hack evtraceroute/evping. But I could not compile they on my Linux box. So I'm looking for some way to build / check RIPE Atlas environment on my machine. So I definitely could install it manually into VirtualBox appliance. On Mon, Nov 9, 2015 at 3:43 PM, Robert Kisteleki <robert at ripe.net> wrote: > Dear All, > > At the risk of assigning more work to myself than I anticipate: there's an > action item on me to come up with some thoughts and questions to the > community about the VM probes. For example: what virtualisation technology > would people prefer (as we cannot support all of them)? How would we manage > these (think of field-upgrades) and how to administer them (at the moment > it's easy, since we supply the whole device with keys and firmware). > > Regards, > Robert > > > On 2015-11-09 13:34, Stephan Wolf wrote: >> +2 for VM probe > -- Sincerely yours, Pavel Odintsov
- Previous message (by thread): [atlas] VM probes
- Next message (by thread): [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]