Time & date 

Wednesday Jun 22 9:00pm Pacific Standard Time, Thursday Jun 23, 2016  9:00am Pakistan time, Thursday June 23  2016 12:00noon Malaysian time, Thursday Jun 23 2016 02:00am Rio Time.  

Coordinates of team members:

See: http://pinger.unimas.my/pinger/contact.php

Attendees

Invitees:

Hassaan Khaliq?, Muhammad Anas Abrar (SEECS); Saqib+, Aqsa (UAF); Johari+, Adnan Khan (UNIMAS);  Badrul,  Ridzuan, Ibrahim (UM); (UTM); Adib, Fatima (UUM); Fizi Jalil (MYREN);   Les+, Bebo, Joao+ (SLAC).

+ Confirmed attendance

- Responded but  Unable to attend: 

? Individual emails sent

Actual attendees:

Joao, Adib, Les

Administration

Android - Bebo 

No update 5/18/2016

Bebo has set up a Github codebase  as a new project. It contains the PingER MA (pinger2.pl and the traceroute/ping server). Anyone  needs to sign up for a Github account (if you don't already have one), so you can be added as a project member.

UUM

No update 5/18/2016

From Adib:

UNIMAS

No update 5/18/2016

Student started last month on the ISO.
pinger.unimas.my does not ping. Reported to Johari.
Adnan has not been assigned any tasks. He is interested in writing papers and will be discussing with Johari on the way forward.
Will revisit traceroute server. No progress 3/12/2016
Update PingER Malaysia site, hope to start in April.
Get back to RPi2 at Datacenter no progress 3/12/216

UAF (Saqib)

There are 4 students:  Aqsa Hameed, Saba Muzamil, Tahseen and Sara Masood. They are all busy this week and last week with exams. We can expect more updates in a couple of weeks time when the exams are done.

    1. pingER  monitoring host on android . I am using perl-android-apk Interpreter to run pearl on android.. it include execution of  3 perl scripts
      1. getdata.pl

      2. ping_data.pl

      3. pinger2.pl

    2. Resources Required

      1. i need ping_data.pl script file and getdata.pl script file.

      2. Joao will provide them via anonymous ftp.

    3. Research Status

Project on Internet performance has not received funding.

Saqib will proceed to install Pinger in UAF Pakistan

UTM 

Saqib's old supervisor  agreed to appoint a master student to take of PingER in UTM. Saqib has emailed  3/9/2016, no progress 4/6/2016, no progress 5/18/2016. 

1.     Currently, Pinger server is located in the faculty server room. Recently, faculty has closed the Server room. Now we have to move it to the University Central Server Room. For this we need support from Prof Johari and Prof Abdul Hanan.

2.     For the M.Sc. student in UTM we have to request again to Prof Hanan and Prof Asri and we need support from Prof Johari.

UM

MYREN

NUST

 

Muhammad Anas Abrar provided an update 6/19/2016: 

pingerqta.pern.edu.pk (DNS resolves to 121.52.157.157) are asking to change the IP to 121.52.157.148, 

Following hosts are down and not responsive. Nodes were contacted many times for identifying their issues. i.e turn on their pinGER Computers but never responded well.

Where as following is the list of Node that are now working:
The following are close to working:

* This host was noted at the 3/9/2016 meeting as being down for the last 30 days.

+ Not seen in June 2016

Les proposes:

 

PingER at SLAC

Joao making the data on FTP to be up-to-date. 

Also has a 4 node cluster with Cloudera manager for Hadoop, Next step are to get impala working for queries.

 Working on the following hosts to be able to gather data

HostStatelast seenStatus
pinger.arn.dzemail 1/30/2016, 2/22/2016, 4/11/2016 no response. Giving up.Nov 2015Does not ping
pinger.unimas.myemail 5/12/2016, fixed 6/16/2016March 2016Does not ping
pingersonar-utm.myren.net.myemail to Fitzi 5/12/2016, fixed May 18, 2016 Does not ping
pinger.unesp.bremail 6/15/2016, fixed 6/20/2016Feb 2016Looked like cronjob not running, cannot ping
pinger.fsksm.utm.myemail 6/15/2016, no responseMay 17Does not ping
www.univ-ouaga.bfUnreliable, but works about 50% time.June 2016Does not ping

Next Meeting

Next meeting:  Wednesday Jul  27 9:00pm Pacific Standard Time, Thursday Jul 28, 2016  9:00am Pakistan time, Thursday Jul 28  2016 12:00noon Malaysian time, Thursday Jul 28 2016 02:00am Rio Standard Time.  

Old Items

Visualization ideas for PingER moved here 5/20/2016

 

 

Huffington Post moved here 3/8/2016

UOA (Saqib) placed here 2/3/2016.

Saqib has a  5  MS students from the Database team

Others

Geolocation

Anjum believes the TULIP Geolocation application  can be improved significantly. At least there are few ideas that we can try. For this, either a group of undergraduate students or an active masters student is required. The resultant work can easily be the thesis of masters level. Who is interested? 

NUST/SEECS Pakistani PingER nodes status

Pink Background indicates host was bad last month, strike through says it is fixed, yellow is an new bad host.

Current status of Pakistani Hosts 7/1/2015

1.    airuniversity.seecs.edu.pk

Down       

Called (Person Not Responding).

 2.    comsatsswl.seecs.edu.pk

Down

Called (Link Issue)

ns3.pieas.edu.pkPingable 

 3.    nuisb.seecs.edu.pk

Down

Called (Not Responding)

 4.    nukhimain.seecs.edu.pk

Down

Called (Will be up within two days)

 5.    pinger.cemb.edu.pk

Pingable

Called (Need Access) 

 6.    pinger.kohat.edu.pk

Down

Email sent to the concern Person (DNS Entry issue) 

 7.    pinger.lhr.nu.edu.pk

Down

Called (Person Not Responding)

 8.    pinger.lcwu.edu.pk

Down

Working now?

 9.    pinger.nca.edu.pk

Down

Called (Will be up within two days)

 10.    pinger.numl.edu.pk

Pingable

Need Visit

 11.    pinger.pern.edu.pk

Down

Need Visit

 12.    pinger.usindh.edu.pk

Down

Called (Person Not Responding)

 13.    pingerisl-fjwu.pern.edu.pk

Down

Need Visit

pingerisl-qau.pern.edu.pkDown 
pingerkhi.pern.edu.pkDown 
pingerlhr.pern.edu.pkDown 

 14.    pingerqta.pern.edu.pk

Pingable

Email sent to the concern person (DNS Entry Issue)

 15.    www.upesh.edu.pk

Pingable

Called (Person not cooperating)

sau.seecs.edu.pkDown 

Is it time to start paring down the list of PingER monitor hosts in Pakistan, starting with those that have been down for a while and despite your efforts they are not cooperating.  One might also look at the coverage by region in Pakistan and try and keep good coverage for all regions.

Traceroute at UTM 5/9/2015

The traceroute problem regarding maximum reachable hops ( i.e. 11 hopes ) may be since the Unix/Linux/OSX  traceroute uses UDP to send the requests. The first request is sent to a particular port (33434), with a ttl  to tell it how many hops to go to.  The ttl starts at 1 is incremented as it tries the next hop, also the port is incremented (up to 33465).  It looks like the first few UDP ports are enabled and then they are blocked. The Windows traceroute uses ICMP to send the probes so does not see the problem.

Linked Open Data

Cristiane reports (7/1/2015): "I am trying to automatize the triplification of PingER data on Kettle. For now, part of the transformation is made on Kettle and another is made by a Java code. Although this solution works for a data sample, is important to have the entire process on Kettle because it facilitates to understand, modify and control the triplification process."

Feb 2015

The plan is still the one seen before (see project proposal), experimenting those alternatives. Right now, they managed to triplify the data according to a new ontology that takes advantage of a combination of a current standard for multidimensional data (called data cube vocabulary) and a revised version of Renan's Moment ontology adaptation. With this we expect to have a better data organization than the previous solution.

They are now preparing a test plan (like a small benchmark) to be used on all alternatives so that we can compare the results accordingly. 

Aug 2014

Renan  finished the new pingerlod web site. The new thing is that it should be much easier now to modify the info texts. What Renan did was to put the texts into a separate file. The new version has been loaded on the server and some text added to describe how to use the map. However there is a bug that prevents it from executing the map. Renan reports that the bugs should be easy to fix. He has talked to his professor who suggested trying RDF Owlink, it should have faster responses to queries. Renan will research this.  It will probably mean reloading the PingER data so is a lot of work, hopefully this will improve performance. Before the rebuild he will make the fixes and provide a new WAR for us to load on pingerlod.slac.stanford.edu. He is also working on documentation (he has finished the ontology and has a nice interactive tool for visualizing it, since the ontology is the core of the data model of our semantic solution, this will be very helpful for anyone who uses our system, both a developer of the system and a possible user) and his thesis. Bebo pointed out that to get publicity and for people to know about the data, we will need to add pingerlod to lod.org.

Things he will soon do regarding documentation:

  1. A task/process flow writing all java classes involved on all those batch jobs;
  2. A Javadoc <http://www.oracle.com/technetwork/java/javase/documentation/index-jsp-135444.html> which will explain all classes and how they are used.

For the Linked Open Data / RDF which is in pre-alpha days, you can go to http://pingerlod.slac.stanford.edu. As can be seen this page is not ready for prime time. However the demos work as long as one carefully elects what to look at:

Renan is using OWLIM as RDF Repository. He is using an evaluation version right now. Renan looked into the price for OWLIM (that excellent RDF Database Management System he told us about). It would cost 1200EUR minimum  (~ 1620 USD, according to Google's rate for today) for a one time eternal license. It seems too expensive. No wonder it is so good. Anyhow, he heard about a different free alternative. Just not sure how good it would be for our PingER data. He will try it out and evaluate. He will also get a new evaluation of the free OWLIM lite.  

He has also made some modifications on the ontology of the project (under supervision of his professor in Rio) hence he  will have to modify the code to load the data accordingly.

Maria and Renan are advancing in some approaches to deal with PingER data, making it easier to be analyzed and integrated. In particular they have been busy studying and evaluating alternatives, analyzing results from the latest benchmarks on NoSQL (including RDF and graph based storages) database management, distributed processing and mediated  solutions over relational databases, and also other experiments with multidimensional analyses on Linked Data.  The new students involved are now understanding better the scenario and they have been interacting with Renan regularly. 

Cristiane has studied the PinGER data and how to cast it into Linked Open Data form. The size of the PingER hourly data for 1998-Sep 2014 archived via FTP in text form amounts to ~ 5.12GB and this corresponds to 15.66*10^9 (billion) triples. Then using 5  triples for each measurement and using Turtle without compression gives us 685 Gbytes or an inflation factor of ~ 200. 

When Christiane made the estimation of PingER triples, she wrote two documents that explain the process but they were in Portuguese. She has written the new versions in English.

Christiane's report is at: Size Inflation of PingER Data for use in PingER LOD

UM

Moved here 3/4/2015:

Ibrahim has setup distributed hadoop clusters. He has 2TB of disk space. Les has provided information on getting a subset of PingER data by anonymous ftp via ftp://ftp.slac.stanford.edu/users/cottrell.  It was put there last September. Information on how the data was put together is at https://confluence.slac.stanford.edu/display/IEPM/Archiving+PingER+data+by+tar+for+retrieval+by+anonymous+ftp. There is information on formatting etc at http://www-iepm.slac.stanford.edu/pinger/tools/retrievedata.html and some on the dataflows at https://confluence.slac.stanford.edu/display/IEPM/PingER+data+flow+at+SLAC. Renan at UFRJ has successfully used this data, he has also characterized the data in terms of bytes/metric per year etc.

Ibrahim has started downloading all zip files in the local machines. 6 weeks ago he downloaded 2 GB of Weather data to test his nodes cluster, he  wrote a simple Java program (Map, Reduce) to find the Average and it was working fine. 

Anjum reported that UM had experienced a TCP syn DOS attack prior to Mar 12th (when an IDS was put in place). It occurred mainly for several days before between the hours on noon- 2pm and 7-7 in the evening (Malaysia time). He suggested looking to see if PingER could spit the effect.  Ibrahim, Les and Anjum will look at. Les analyzed the data and sent it to Anjum

NUST

The following is from Samad 2/24/2015.

Follow up from workshop

The Next step in funding is to go for bigger research funding, such as LRGS or eScience. Such proposals must lead to publications in high quality journals. They will need an infrastructure such as the one we are building. We can use the upcoming workshop (1 specific session) to brainstorm and come up with such proposal. We need to do some groundwork before that as well. Johari will take the lead in putting together 1/2 page descriptions of the potential research projects. 

  1. Need to identify a few key areas of research related to PingER Malaysia Initiative and this can be shared/publicized through the website. These might include using the infrastructure and data for: anomaly detection; correlation of performance across multiple routes; and for GeoLocation. Future projects as Les listed in Confluence herehttps://confluence.slac.stanford.edu/display/IEPM/Future+Projects can also be a good start and also Bebo's suggestion. 
  2. Need to synchronize and share research proposals so as not to duplicate research works. how to share? Maybe not through the website, or maybe can create a member only section of the website to share sensitive data such as research proposal?

Anjum suggested Saqib,  Badrul and Johari put together a paper on user experiences with using the Internet in Malaysia as seen from Malaysian universities. In particular round trip time, losses, jitter, reliability, routing/peering, in particular anomalies, and the impact on VoIP, throughput etc.  It would be good to engage someone from MYREN.

Ibrahim

Ibrahim Abaker  is planning to work on a topic initially entitled " leveraging pingER big data with a modified pingtable for event-correlation and clustering".  Ibrahim has a proposal, see https://confluence.slac.stanford.edu/download/attachments/17162/leveraging+pingER+big+data+with+a+modified+pingtable+for+event-correlation+and+clustering.docx. Ibrahim reports 7/15/2014 "I have spent the last few months trying to understand the concept of big data storage and its retrieval as well as the traditional approach of storing RDF data. I have integrated a single hadoop cluster in our cloud. but for this project we need multiple clusters, which I have already discussed with Dr. Badrul and he will provide me with big storage for the experiment." No Update 8/20/2014.

"I have come up with initial proposed solution model. This model consists of several parts. The upper parts of the Figure below shows the data source, in which PingER data will be convert into RDF format. Then the data pre-processor will take care of converting RDF/XML into N-triples serialization formats using N-triples convertor module. This N-triple file of an RDF graph will be as an input and stores the triples in storage as a key value pair using MapReduce jobs"

Potential projects

See list of Projects

 

1)  pingER  monitoring host on android .

 

 I am using perl-android-apk Interpreter to run pearl on android.

 

it include execution of  3 pearl scripts

 

*             PingER2.pl

               

*             ping_data.pl

               

*             getdata.pl

               

 

 

 

2) Resources Required

 i need ping_data.pl script file and get data.pl script file .

 

 

3) Research Status

   Perl-android-interpreter is not executing .pl file mainly because old Perl version (Perl 5.10) which is not comparable with android lollipop 5.0 version, i am compiling  Perl .5.22.0 for android ,it may solve issue.