Re: [atlas] RIPE Atlas anchor self assembly

2015-11-10 Thread Daniel Karrenberg
No, see the other discussion. On 10.11.15 17:31 , Daniel Baeza (Red y Sistemas TVT) wrote: > So... if we give you access to a CentOS VM, you can make it Anchor? :) > > El 10/11/2015 a las 17:01, Philip Homburg escribió: >> On 2015/11/10 16:56 , Colin Johnston wrote: >>> Can we have link to image

Re: [atlas] RIPE Atlas anchor self assembly

2015-11-10 Thread Daniel Baeza (Red y Sistemas TVT)
So... if we give you access to a CentOS VM, you can make it Anchor? :) El 10/11/2015 a las 17:01, Philip Homburg escribió: On 2015/11/10 16:56 , Colin Johnston wrote: Can we have link to image so we can can convert to a VM image for hosting via virtual instead :) maybe useful cost saving :)

Re: [atlas] RIPE Atlas anchor self assembly

2015-11-10 Thread Philip Homburg
On 2015/11/10 16:56 , Colin Johnston wrote: > Can we have link to image so we can can convert to a VM image for hosting via > virtual instead :) > > maybe useful cost saving :) The image contains not much more than CentOS, a compiled version of the Atlas source code (which is published) and a bu

Re: [atlas] RIPE Atlas anchor self assembly

2015-11-10 Thread Colin Johnston
Can we have link to image so we can can convert to a VM image for hosting via virtual instead :) maybe useful cost saving :) Colin > On 10 Nov 2015, at 15:40, Michela Galante wrote: > > Hi everyone, > > Some people on this list have been asking about the possibility of purchasing > hardware

[atlas] RIPE Atlas anchor self assembly

2015-11-10 Thread Michela Galante
Hi everyone, Some people on this list have been asking about the possibility of purchasing hardware for a RIPE Atlas anchor by themselves and assembling it. This is indeed possible. However we do not recommend it because if the assembled hardware is not exactly to our specifications, we will no

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Budiwijaya
So, is this mean that we can build our soekris hardware by our self? (we don't have to import any soekris from outside). If this true, then it will be an opportunity for any network that want to host an anchor but limited by import issues. On Tue, Nov 10, 2015 at 5:39 PM, Pavel Odintsov wrote: >

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Philip Homburg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015/11/10 14:05 , Gert Doering wrote: > Hi, > > On Tue, Nov 10, 2015 at 01:50:41PM +0100, Philip Homburg wrote: >> For ordinary probes, we have absolutely no control over the >> network. Probe hosts don't have to guarantee anything. So I >> wond

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Philip Homburg
On 2015/11/10 14:01 , Colin Johnston wrote: >> One way of looking at it, are the people who want a VM willing to >> guarantee that the VM performs better than the current Soekris boxes we >> use for anchors? And is there is way of monitoring that they live up to >> their promises. >> > A well manag

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Nick Hilliard
On 10/11/2015 13:01, Colin Johnston wrote: > A well managed vm this is the key point. the ripe atlas people have no control over the hypervisor management, which is important from a measurement point of view. Nick

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Gert Doering
Hi, On Tue, Nov 10, 2015 at 01:50:41PM +0100, Philip Homburg wrote: > For ordinary probes, we have absolutely no control over the network. > Probe hosts don't have to guarantee anything. So I wonder if blackbox > testing would even allow distinguishing between an overloaded VM and a > probe on a v

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Colin Johnston
reply inline > On 10 Nov 2015, at 12:50, Philip Homburg wrote: > > On 2015/11/10 13:36 , Colin Johnston wrote: >> After having lived and still work in a Solaris physical metal land, I took >> onboard the virtual machine world for a webservice/emailservice. >> The virtual world is cheaper in lon

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Philip Homburg
On 2015/11/10 13:36 , Colin Johnston wrote: > After having lived and still work in a Solaris physical metal land, I took > onboard the virtual machine world for a webservice/emailservice. > The virtual world is cheaper in long run. > However does require a vm/ov image. > > I think it is important

Re: [atlas] Sharing credits with colleagues

2015-11-10 Thread Oliver Haake
My colleagues can also ask me for credits, but the point is, that I don't want to do this manually. So the idea that Robert presented in his reply sounds quite good. On 10.11.2015 13:42, Jared Mauch wrote: > Or you can ask me for credits. I transfer credits to people who ask. My > credit cup

Re: [atlas] Feature request for IP record route feature in RIPE Atlas

2015-11-10 Thread Pavel Odintsov
Thanks! I will try to run it on CentOS VirtualBox vm. On Mon, Nov 9, 2015 at 4:10 PM, Philip Homburg wrote: > On 2015/11/09 10:04 , Pavel Odintsov wrote: >> But RIPE Atlas offer really huge coverage over the World and we could >> reach really any host with <7 hops. But we haven't this feature in

Re: [atlas] Sharing credits with colleagues

2015-11-10 Thread Jared Mauch
Or you can ask me for credits. I transfer credits to people who ask. My credit cup runneth over. - Jared > On Nov 9, 2015, at 8:02 AM, Oliver Haake wrote: > > Thank you Robert, that sounds awesome. > Keep up the good work. > > > Cheers, > Oliver > > > > > > On 09.11.2015 13:27, Robert

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Colin Johnston
> On 10 Nov 2015, at 12:20, Wilfried Woeber wrote: > > > On 2015-11-10 11:18, Stephan Wolf wrote: > >> ANCHOR as an VM would really make sense. >> What do you think about this ? > > I think this would really be a BAD idea! The anchors are meant to be more > capable and more stable than the ca

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Wilfried Woeber
On 2015-11-10 11:18, Stephan Wolf wrote: > ANCHOR as an VM would really make sense. > What do you think about this ? I think this would really be a BAD idea! The anchors are meant to be more capable and more stable than the candy probes. Messing around with that concept should not be done, imho.

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Gert Doering
Hi, On Tue, Nov 10, 2015 at 11:18:37AM +0100, Stephan Wolf wrote: > ANCHOR as an VM would really make sense. > What do you think about this ? Even less so than a probe - as the anchor needs to provide reliable and robust measurements *and* responses to probes. Gert Doering -- NetMaster -

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Bajpai, Vaibhav
> On 10 Nov 2015, at 11:18, Stephan Wolf wrote: > > Sure, PROBES as an VM in e.g. overloaded environments are a problem. So > Probes on a VM = can result in some troubles in the existing Atlas model. > To > make a "second class" probes I agree that this takes too much efforts. >

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Pavel Odintsov
Hello! Maybe we could fix import issues with some vendor? We have really huge and good shop of network hardware here: http://shop.nag.ru If they could offer Soekris platform could be fine. On Tue, Nov 10, 2015 at 1:30 PM, Daniel Karrenberg wrote: > Pavel, > > it appears that my information is o

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Daniel Karrenberg
Pavel, it appears that my information is out-dated. You are right one needs to import them these days. I realise that this is awkward and expensive, but it appears to be possible. Maybe rather than wasting time on VMs we should consider a new type of anchor which is more readily available everywh

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Nick Hilliard
On 10/11/2015 10:18, Stephan Wolf wrote: > ANCHOR as an VM would really make sense. > What do you think about this ? it depends how the hypervisor is managed. I've seen some completely overloaded hypervisors where the VM performance is terrible. At least with the hardware probe, the RIPE NCC con

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Stephan Wolf
Sure, PROBES as an VM in e.g. overloaded environments are a problem. So Probes on a VM = can result in some troubles in the existing Atlas model. To make a "second class" probes I agree that this takes too much efforts. ANCHOR as an VM would really make sense. What do you think about this ? PACKA

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Bajpai, Vaibhav
Hello, As a researcher, I will have to filter out these VM probes unless there is considerable evidence that VM probes are able to produce results comparable to hardware probes. Note, calibrating probes is really hard and it takes time and effort [1, 2]. The idea of using these VM probes for "sec

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Sebastian Neuner
Hi all, first of all, I see a few problems with VM probes. It's important for the Atlas measurements to be comparable, which can be a problem if you just run a virtual probe on someones hardware in a datacenter somewhere. Or to put it simple: we want to measure networks, not virtualization hardwa

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Jaap Akkerhuis
Daniel Karrenberg writes: > At this time are 485 connected probes and two connected anchors in > Russia. As far as I know Soekris boxes can be bought in Russia. And there are regularly atlas ambassadors in Russia. I returned with 3 probes from ENOG-10 because I couldn't get rid of them.

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Pavel Odintsov
Hello! Awesome! Could you share where we could bought it? I will share this information with local community. On Tue, Nov 10, 2015 at 12:36 PM, Daniel Karrenberg wrote: > At this time are 485 connected probes and two connected anchors in > Russia. As far as I know Soekris boxes can be bought in

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Daniel Karrenberg
At this time are 485 connected probes and two connected anchors in Russia. As far as I know Soekris boxes can be bought in Russia. Daniel On 10.11.15 10:07 , Pavel Odintsov wrote: > Hello, Community! > > I like idea about VM based Anchor's. > > For example in Russia we have so much companies wh

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Pavel Odintsov
Hello, Community! I like idea about VM based Anchor's. For example in Russia we have so much companies who really want to host RIPE Anchor hosting but it's really hard due to so much bureaucracy for computer hardware import. It's really sophisticated and long task. VM based Anchors could help in

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Gert Doering
Hi, On Tue, Nov 10, 2015 at 09:33:01AM +0100, Daniel Karrenberg wrote: > >From my personal, informal assessment I advise against supporting VMs. I > recommend a thorough assessment of the data quality, the costs and the > effects on RIPE Atlas as a whole before diving into soloutioneering. From e

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

2015-11-10 Thread Daniel Karrenberg
I understand the temptation of "easy deployment". The con-s also have been outlined ad nauseam. So let me repeat this only once: We should all assess this thoroughly before diving into it. What quality of data we expect from VMs? What is the real cost of *supporting* VMs? The main costs are not in