...
Prof Abhay Basal, A. Sai Sabitha, ... Shiv Rajappa, Rohan - Amity; Les, Bebo SLAC
General
The students will be preparing for andf taking finals between no and May 15th. Probably the next meeting will be in the 3rd week of May.
PingER MA - Les
Installation Overview.This is proceeding. They have a working pinger2.pl. They have a public DNS pingeramity.it. They have installed ping_data.pl, it is working:
...
[cottrell@pinger ~]$ nslookup pingeramity.in
Server: 134.79.111.111
Address: 134.79.111.111#53
Non-authoritative answer:
Name: pingeramity.in
Address: 202.12.103.71
Name: pingeramity.in
Address: 173.193.105.245
The host has been un-pingable for the last two days. They have been experiencing Ethernet problems that they hope to solve in the coming day. Then we will retest.
Traceroute/ping servers - Les
...
This was at least partially due to the host's environment variable REMOTE_ADDR=10.0.253.1 whereas it should be the public address of the remote host but. 10.0.253.1 is a private address so here is no way to traceroute to it. THis has probably been fixed with the pingeramity.in DNS registration. However the host is unpingable.
They will look at setting the REMOTE_ADDR environment variable.
Android implementation of Pinger Measurement Agent - Bebo
See here. Also see the notes from the meeting on PingER/Android with Sara and Saqib in Pakistan who are working on this.
They have put together an app written in java that can take a list of hosts and make a set of pings to each in turn. The output appears as:
Pinger2.pl uses the standard Linux ping to make up to 30 pings stopping when it has received 10 responses, so the ping command will need modifying (hopefully there is a java ping option to support this). In addition the output will need to be parsed to produce the pinger2.pl output format. It may be easier to take the pinger2.pl code and run a it under a perl interpreter. This is the approach Sara is taking in Pakistan. They will examine this. If they find serious problems they will communicate that so it can be shared with Sara. Also they will need to check the pinger2.pl documentation to ensure that a java version does the exactly same thing and has the same features.
They do not believe there is a problem with running the equivalent of a cron job to schedule the measurements each half hour.
Apart from this they will look at putting together a proxy that the Android can send the recent data to. Then the SLAC archive site can gather the data from the proxy. The proxy could be replicated at a second site for high availability. Depending on reliability the android should preserve a cache of the most recent data so it can be re-sent later. The least recently used data can be flushed asynchronously.
Scope Overview of PingER Linked Open Data (LOD) and Web Observatory - Bebo
...