Time & date
Next meeting Wednesday February 19th 2014 8:00pm Pacific Standard Time, Thursday February 20th 2014 9:00am Pakistan time, Thursday February 20th, 2014 noon Malaysian time, Thursday 20th February, 2014 02:00am Rio Standard Time.
Attendees
Invitees:
Anjum+, Hassaan Khaliq-, Kashif-, Raja+, Johari+, Nara, Abdullah, Badrul, Ridzuan-, Hanan, Saqib-, Adib, Les+, Renan, Bebo-
+ Confirmed attendance
- Responded but Unable to attend:
Actual attendees:
Administration
Anjum is at UM. He does have access to the Internet from the Lab but its a shared place and he cannot attend meetings while in the Lab. For meetings, either he shall attend it from his home, or from the common room of the building.
- Johari proposes that UTM host a PingER workshop in 2014, maybe associated with another conference.
Adib suggested a summer school that is aimed at graduate students and researchers from different disciplines where everyone needs to be present for team presentations based on case studies/assignments given to each team. Each team will be mentored by one professional researcher (from PingER Current Member) to guide and advise. The Summer School activities will include: Keynote talk, Presentations on current projects related to Pinger that open up challenges for students to solve and address, and case studies (assignments based on the presentations) for each team of students.
- Johari talked to Adib who is interested in hosting the workshop at UUM. They believe that with Anjum in Malaysia, the main cost is for Les. Johari shared the information from the previous 2 workshops and it is believed it is good value for money. Given this, it appears the funding required is achievable. There may also be a possibility for a presentation by Les to a more public audience at the ITU Research Center, as well as the possibility of getting sponsors and requiring a registration fee for private sector people. Adib will put together a proposal and take it to the UUM Vice Chancellor.
Renan
Renan realized that testing on Virtuoso is going to take longer than he thought because of the big number of triples. He did not have enough time to continue his tests.
Renan is writing the paper. He has completed 3 pages of 7. He hopes to have it finished soon, since the submission date is March 1st.
Renan did not not see Vinicius (the admin of the UFRJ PingER monitor). We can try to contact him via email again (maybe in the end of February?). If he doesn´t reply, Renan can try to talk to him in person again.
It would be good if somebody else was able to work with Renan to move PingER LOD forward. However we think the performance issue has to be resolved first.
UM
UM appears to be experiencing very high packet losses (>4%). We need help in understanding these. It does not look like simple congestion since the jitter and RTT is staying low. Saqib needs assistance from Badrul as part of his case study of Malaysia. Badrul writes: "UM is now currently changing the new policy regarding the bandwidth and connection. They are upgrading the switch and router to a new router - mostly every weekend they shut down the network. therefore we are now having some difficulty." Saqib has identified what appear to be losses starting at a JARING router in KL. Badrul will run some mtr traceorute/pings to various sites.
Badrul plans for his undergraduate student (Abdulrahim Haroun Ali) to have a draft paper on anomalies in PingER measurements to share for review by the end of semester (January). Update?
Ridzuan is still in the configuration process for communication between the Hadoop nodes. Need some troubleshooting at the moment.
Ibrahim Abaker is planning to work on topic initially entitled " leveraging pingER big data with a modified pingtable for event-correlation and clustering", The purpose of this project is to make Pinger more efficient and more scalable to retrieve and analysis pingER raw data. Consequently it may improve pinger data store. He is planning to use key-value store model with high expandability and shorter query response time. The benefit of such project will help in the design of real time analysis and distributed pinger data across multiple servers for analysis. Les has sent him a pointer to documentation on the data flow at SLAC and also listings of pingtable.pl and associated script. He is currently writing a proposal, which will contain a problem statement, objectives, scope and the approach to tackle the problem. He asked: how much PingER data is captured and stored so far (~ 1TByte)? Is there a published paper (see http://www-iepm.slac.stanford.edu/paperwork/ieee/ieee.pdf)?
UNIMAS
No progress 2/19/2014.
The Raspberry Pi is at the data centre, but due to miscommunication, the public ip which was previously assigned to the rasp pi unit has been assigned to another server. So now Johari has to wait for the ip to be reassigned back to rasp pi unit and give new ip to the other server. They suggested a new ip for the rasp pi unit but Johari wanted to have the old one so that we do not have to update the record at slac for the archival process, etc
The tool to enable synchronizing Malaysian monitors is completed. It provides the ability to add, edit and delete nodes. Raja has tested and after a mod was made to replace a private IP address it is working well. Badrul and Saqib need to try it out.
The traceroute server at http://pinger2.unimas.my/cgi-bin/traceroute.pl has the same problem as before. They know (sort of) the problem but haven't got the chance to rectify it (mapping NAT address, needs to be added). There is no progress 12/4/2013, 1/8/2013, 1.22.2014, 2/5/2014. Now that the historical traceroutes are working for UM (see below) there is an extra incentive to get the reverse traceroute working at UTM and UNIMAS
Johari has a research student who finalized a proposal in order to officially apply for his masters. He will start in February. He is currently working on threshold/anomaly detection, and will extend to correlating performance over multiple routes. He will share the proposal with Les and others in the next 2 weeks to get reviews.
UTM
No progress 2/19/2014
Saqib received an email regarding the successful selection of research assistant-ship at UTM. However, he is waiting for an official offer letter from research management center.
Saqib is working with the IT department in UTM to solve the problems of delays in traceroute. They have a new ISP. Now the pinger server is working with single static IP (161.139.68.188) both for intranet and internet. Previous internet IP 161.139.146.158 is removed. Again given the new historical traceroute facility (see below), it is important to get this working.
- No load balancing is involved as UTM is working with single ISP.
- Still the problem of the delay in traceroute is not solved. It appears to be due to the DNS lookup delay.
Saqib has started a case study of Malaysian hosts seen from Malaysian Monitors. The case study is identifying the need for the Malaysian monitors to collect traceroutes to their target hosts daily. SLAC has a script to facilitate this, for routes seen from SLAC, that could be adapted for other sites. The latest copy of the word file was shared with Badrul and Johari. No update 2/5/2014.
UUM
Dec 4, 2013: The director of computer centre has agreed to support this collaboration and already appointed one staff to be with us during the configuration. Next step, Adib needs to discuss with Prof. Suhaidi to dedicate one PC OR get support from Badrul grant to buy one PC for this purpose or have a bake sale and buy a Raspberry Pi. Adib will do his best to setup PingER monitoring host at UUM before the end of this year. Adib was not on the meeting. He provided an update by email: "Still waiting to get PC. But they promise to provide one very soon. it is totally beyond my control." Regarding the meeting, Adib will attend the upcoming meetings once UUM pinger host is up. No update 2/5/2014.
NUST
At the Connect Asia Pacific Summit in Bangkok in Januaryt and seeing the project "Mapping the pan Asia Pacific information Superhighway and closing gaps in infrastructure connectivity" Shahryar found that very much related to the work in the PingER project. So Shahryar sent email to a UN agency for a possible collaboration with them on PingER project. He has heard nothing so he will write a detailed proposal and then should contact them again. No update 2/5/2014.
Hassaan reports that they have established contact with people in Bahawalpur. The contact person forwarded the request to higher authorities for approval of PingER deployment.
The contact at Sahiwal did the installation of PingER node by himself but data is not being collected, so we are in contact to resolve the issue. Kashif believes he missed some Linux updates. Today is holiday here and he will do the trouble shooting on 6th Feb.
We were gathering data from Pingerisl-air (this is continuing to work), and Quest (stopped working Feb 13)
We are still unable to gather data from airuniversity, buitms, cae, duhs, pinger.pern.edu.pk, pingerisl-qau, sau.seecs.edu.pk , uaf.
Monitors Status
Airuniversity New installation will be install in a week
Buitms Problem in hardware, they are trying to fix it. System Replacement Required
Cae Problem with IP, they are trying to resolve it
Duhs They are purchasing new servers in two week time
pinger.pern.edu.pk since Jan 13, System not booting
Pingerisl-qau Contact person is still on leave. He is now busy in other pending works.
sau.seecs.edu.pk for all of January. Contact person is not attending
Uaf Problem in system, visit approval for Faisalabad University in progress. Approved for 12th Feb
Kashif reports (2/19/2014): "We are in a process of shifting us along with equipment to another lab from a week. Due to this transition process and new installations, Joun could not contact further to the contact persons about the down PingER Nodes. This shifting process will complete on coming Friday and after that i will be able to update you about the task on NUST part."
TULIP - Raja
Please try out http://www-wanmon.slac.stanford.edu/cgi-wrap/reflector.cgi?function=vtrace It is a visual traceroute. It uses TULIP to locate the routers. It is in beta test and needs testing by friendly users. We are looking to add a link to it from the perfSONAR home page.
We have sent a reminder email to Yahoo giving them an update on TULIP and how it might be extended to meet their needs. They have responded, they appear to be interested. We are trying to interest them in providing landmarks. No update 2/18/2013.
Raja has added 56 more perfSONAR landmarks, most of them are in North America. Currently we have 298 active landmarks (from total of 918).
PingER at SLAC
We put together a slide presentation to ICFA in Geneva, to be given by Harvey Newman. It is at: http://www.slac.stanford.edu/xorg/icfa/icfa-net-paper-jan14/ICFASCICPresentation_MonitoringGroupSlides20140205.pptx
Raja has also re-written the historical traceroute facility that takes nightly traceroutes and allows one to retrieve and compare them. He then extended it to use the reverse traceroute facility to provide histories for NUST, CERN, UM as well as SLAC. When the UNIMAS and UTM traceroutes work, we can include them. See for example http://www-wanmon.slac.stanford.edu/cgi-wrap/traceroutearchive.cgi
Old Items
Linked Open Data
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 responeses 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:
- A task/process flow writing all java classes involved on all those batch jobs;
- 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:
- Click on Visualizations, there are two choices:
- Multiple Network Metrics: Click on the image: gives a form, choose from Node pinger.slac.stanford.edu pinging to www.ihep.ac.cn, time parameters yearly, 2006 2012, metrics throughput, Average RTT Packet loss and display format Plot graph, then click on submit. In a few seconds time series graph should come up. Mouse over to see details of values at each x value (year).
- A mashup of network metrics x university metrics Click on image: gives another form, pinging from pinger.slac.stanford.edu, School metric number of students, time metric years 2006 2012, display format plot graph, click on submit. Longer wait, after about 35 seconds a google map should show up. Click on "Click for help." Area of dots = number of students, darkness of dots = throughput (lighter is better), inscribing circle color gives university type (public, private etc.) Click on circle for information on university etc.
- Renan will be working on providing documentation on the programs, in particular the install guide for the repository and web site etc. This will assist the person who takes this over.
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.
Renan has provided a 4 page Appendix on PingERLOD to the ICFA report. This is also available at PingER LOD Overview
Raspberry Pi
A quick comparison of the performance of the two hosts (raspberry pi and regular UNIMAS host) without statistical quantification is available at https://confluence.slac.stanford.edu/display/IEPM/Comparison+of+PinGER+RTTs+from+UNIMAS+monitors+N4+and+RASPBERRY. A page has been created to compare the hardware spec between the pinger.unimas.my node (Intel architecture) and the pinger2.unimas.my node (Raspberry Pi ARM architecture), available from the unimas pinger website at http://pinger.unimas.my/pinger/hardware.php. There is a link to hardware.php in the Comparison+of+PinGER+RTTs+from+UNIMAS+monitors+N4+and+RASPBERRY web page.
Tulip
We are looking at submitting a paper to IMC 2014. April 30, 2014 (see http://conferences2.sigcomm.org/imc/2014/cfp.html) is the submission date. this would discuss how TULIP works and share our experiences. Thus we might focus on: managing the appearance/disappearance of landmarks; the selecting of optimum timeouts for speedup plus any other ideas for speedup; where one could go next (e.g. colocation of landmarks on Yahoo, Google, Hotmail ... sites; impacts of heavy use and scaling (e.g. need for cluster for reflector, multiple landmarks at sites to not overwhelm a given landmark); concerns about network utilization); the relation of accuracy to landmark density (big item). Also more on potential uses such as visual traceroute, identifying proxies. Also maybe a bit more on the actual user interface (results from multiple sources besides TULIP) and implementation (parallel threads, tiering and adding new regions). The paper would assume we have a working TULIP as described in the other paper.
Follow up from workshop
- Hossein Javedani of UTM is interested in anomalous event detection with PingER data. Information on this is available at https://confluence.slac.stanford.edu/display/IEPM/Event+Detection. We have sent him a couple of papers and how to access the PingER data. Hossein and Badrul have been put in contact. Is there an update Badrul?
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.
- 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.
- 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.
Potential projects
Future meeting - Les
Next meeting Wednesday March 5th 2014 8:00pm Pacific Standard Time, Thursday March 6th 2014 9:00am Pakistan time, Thursday March 6th, 2014 noon Malaysian time, Thursday March 6th, 2014 02:00am Rio Standard Time.