...
- The traceroute server at Pune has moved to a new host.
- We are working on getting pinger2.pl working at Sarawak. The pinger.xml page needs to be fixed
- PingER archive site: Ghulam and Farhan have created two ERDs. One is a simple design (relatively inefficient) and another is a complex design (relatively efficient though it might introduce some redundancy) with multiple normalized tables that can be joined. They have created MySQL databases following both ERDs and have done some stress testing. The simple design is faster to load, the more complex design is faster to load data from. They will probably go with the more complex design. Umar went through the URDs, and requested a document on what they have done.
TULIP
- With the move to the new host Faisal had to get a new cookie to allow scriptroute to run scripts on the PlanetLab infrastructure. Still needs testing.
- Get the MatLab license at SEECS and put up a CGB server using it. Do not have license for MatLab will do on own machines to test and will migrate when have license. Zafar will contact Arshad and Ali. Basically the client will call the reflector with the target. The reflector will return the landmarks and RTTs. The client will then call the CBG/MatLab server with the relevant RTTs, lat/longs etc. Update
- CBG Bilal went to home time after exams, so far changed CBG to integrate into TULIP. Hoped to get to him by end of last week, when he returns meet on Monday. Update
...
- Faisal is working with Yee.
- Zafar - deploy PerfSONAR nodes at SEECS. Second step is to find whether the same can be done at HEC on PERN's network. It is working, congratulations!
Possible projects
Wiki Markup
- Extend the NODEDETAILS data base to allow entry support for whether the host is currenty pingable.
Wiki Markup - Improve the PingER2 installation procedures to make it more robust. This might be something for the person(s) in Pakistan who are responsible for installing PingER2 at the Pakistani monitoring sites. They probably have found where the failures occurs. Also look at the FAQ, and ping_data.pl which has been improved to assist in debugging, could it be further improved (e.g. provide access to the httpd.conf file so one can see if it properly configured)? There are 2 students working on the PingER archive. *Is this something they could work on?*
- Fix PingER archiving/analysis package to be IPv6 conformant. Will build a proposal for an IPv6 testbed. They will try various transition techniques. A proposal has been prepared and that has been submitted to PTA. Adnan is a co PI. It is being evaluated today. A small testbed has been established in SEECS and the plan to shift some of the network to IPv6. Bilal is part of 3 students involved with PingER and they will be involved with IPv6. They are porting the PingER archive site site to using a database. They have redeveloped the archive site using Umar's documentation. They have set up a small test archive site. They have gathering, archiving, analysis. They will design a new database. They will also try a port of PingER to IPv6.
- Look at RRD event detection based on thresholds and how to extend, maybe adding plateau algorithm. Umar's algorithm did not work in a predictable manner.
- Provide near realtime plots of current pinger data using getdata_all.pl/wget. It will work as a CGI script with a form to select the host, the ping size, and the time frame to plot. It will use wget or getdata_all.pl to get the relevant data and possibly RRD/smokeping to display the data. Anybody interested?
...