Hi! I just found an old thread about virtual probes: https://www.ripe.net/ripe/mail/archives/ripe-atlas/2013-June/000849.html I second the problems of virtual hosts and that the results may not as good as other probes result, but there is a big advantage for virtual probes - I can host them in the cloud. For example, I just wanted to debug routing issues from the Microsoft Cloud in Brazil to our server. Unfortunately there are no probes in this Cloud's AS. With a virtual probe it would be quite easy. I order an VM with Microsoft, and have my probe in the chosen datacenter. The probe could be tagged with "VM" to show that it is running on shared resources. Of course the VM will produce extra costs, but there may be sponsors, and the smallest VM is usually enough. For example , one possibility would be, that the sponsor donates the money, e.g. 10-20€ per month, and chooses the cloud location. RIPE will then rent the VMs and run the probes. With several sponsors we could get a nice cloud coverage, and we could deploy probes in networks where the provider does not want to hosts physical probes. regards Klaus
I have non-atlas probes at all EC2 centres. Definitely support virtualised Atlas. On Friday, March 27, 2015, Klaus Darilion <klaus.mailinglists@pernau.at> wrote:
Hi!
I just found an old thread about virtual probes: https://www.ripe.net/ripe/mail/archives/ripe-atlas/2013-June/000849.html
I second the problems of virtual hosts and that the results may not as good as other probes result, but there is a big advantage for virtual probes - I can host them in the cloud.
For example, I just wanted to debug routing issues from the Microsoft Cloud in Brazil to our server. Unfortunately there are no probes in this Cloud's AS. With a virtual probe it would be quite easy. I order an VM with Microsoft, and have my probe in the chosen datacenter. The probe could be tagged with "VM" to show that it is running on shared resources.
Of course the VM will produce extra costs, but there may be sponsors, and the smallest VM is usually enough. For example , one possibility would be, that the sponsor donates the money, e.g. 10-20€ per month, and chooses the cloud location. RIPE will then rent the VMs and run the probes. With several sponsors we could get a nice cloud coverage, and we could deploy probes in networks where the provider does not want to hosts physical probes.
regards Klaus
Although I still like the idea of virtual probes, I found out that it wouldn't help me in this case, as Microsoft's cloud block ICMP traffic. :-( regards Klaus On 27.03.2015 09:30, Klaus Darilion wrote:
Hi!
I just found an old thread about virtual probes: https://www.ripe.net/ripe/mail/archives/ripe-atlas/2013-June/000849.html
I second the problems of virtual hosts and that the results may not as good as other probes result, but there is a big advantage for virtual probes - I can host them in the cloud.
For example, I just wanted to debug routing issues from the Microsoft Cloud in Brazil to our server. Unfortunately there are no probes in this Cloud's AS. With a virtual probe it would be quite easy. I order an VM with Microsoft, and have my probe in the chosen datacenter. The probe could be tagged with "VM" to show that it is running on shared resources.
Of course the VM will produce extra costs, but there may be sponsors, and the smallest VM is usually enough. For example , one possibility would be, that the sponsor donates the money, e.g. 10-20€ per month, and chooses the cloud location. RIPE will then rent the VMs and run the probes. With several sponsors we could get a nice cloud coverage, and we could deploy probes in networks where the provider does not want to hosts physical probes.
regards Klaus
As one who supported this in the first place I think definitely should be taken up a due to cost saving and b due to power savings. the virtual machine may affect measurement times to a extent but you need to understand that there maybe virtual routers/virtual firewalls in the network path so don’t blame just the source vm machine also virtual probes could help to identify vm environment performance problems Colin
On 27 Mar 2015, at 08:30, Klaus Darilion <klaus.mailinglists@pernau.at> wrote:
Hi!
I just found an old thread about virtual probes: https://www.ripe.net/ripe/mail/archives/ripe-atlas/2013-June/000849.html
I second the problems of virtual hosts and that the results may not as good as other probes result, but there is a big advantage for virtual probes - I can host them in the cloud.
For example, I just wanted to debug routing issues from the Microsoft Cloud in Brazil to our server. Unfortunately there are no probes in this Cloud's AS. With a virtual probe it would be quite easy. I order an VM with Microsoft, and have my probe in the chosen datacenter. The probe could be tagged with "VM" to show that it is running on shared resources.
Of course the VM will produce extra costs, but there may be sponsors, and the smallest VM is usually enough. For example , one possibility would be, that the sponsor donates the money, e.g. 10-20€ per month, and chooses the cloud location. RIPE will then rent the VMs and run the probes. With several sponsors we could get a nice cloud coverage, and we could deploy probes in networks where the provider does not want to hosts physical probes.
regards Klaus
Hi, thanks for bringing this up again. We will have to consider our options and come up with a way forward with this. We will let you know soon with our implementation plan. Kind Regards, Andreas Strikos RIPE NCC On 28/03/15 14:30, Colin Johnston wrote:
As one who supported this in the first place I think definitely should be taken up a due to cost saving and b due to power savings.
the virtual machine may affect measurement times to a extent but you need to understand that there maybe virtual routers/virtual firewalls in the network path so don’t blame just the source vm machine
also virtual probes could help to identify vm environment performance problems
Colin
On 27 Mar 2015, at 08:30, Klaus Darilion <klaus.mailinglists@pernau.at> wrote:
Hi!
I just found an old thread about virtual probes: https://www.ripe.net/ripe/mail/archives/ripe-atlas/2013-June/000849.html
I second the problems of virtual hosts and that the results may not as good as other probes result, but there is a big advantage for virtual probes - I can host them in the cloud.
For example, I just wanted to debug routing issues from the Microsoft Cloud in Brazil to our server. Unfortunately there are no probes in this Cloud's AS. With a virtual probe it would be quite easy. I order an VM with Microsoft, and have my probe in the chosen datacenter. The probe could be tagged with "VM" to show that it is running on shared resources.
Of course the VM will produce extra costs, but there may be sponsors, and the smallest VM is usually enough. For example , one possibility would be, that the sponsor donates the money, e.g. 10-20€ per month, and chooses the cloud location. RIPE will then rent the VMs and run the probes. With several sponsors we could get a nice cloud coverage, and we could deploy probes in networks where the provider does not want to hosts physical probes.
regards Klaus
participants (4)
-
Andreas Strikos -
Colin Johnston -
Jonathan Brewer -
Klaus Darilion