Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Anjum, Hassaan Khaliq, Kashif, Raja+,  Johari, Nara, Abdullah, Badrul, Ridzuan+, Ibrahim, Hanan, Saqib+, Adib, Les+, Renan, Bebo

...

Ridzuan has put together a rough proposal to use Hadoop to store and make available PingER data.  There is a rough draft at: https://confluence.slac.stanford.edu/download/attachments/17162/leveraging%20pingER%20big%20data%20with%20a%20modified%20pingtable%20for%20event-correlation%20and%20clustering.docx. Ridzuan requested a copy of the PingER data.  Les & Raja put together a repository of the minimum_rtt by hour data since Jan 1998 and made it available by FTP.

There was a discussion about using hadoop and other hosts joining. Also the MYREN cloud  has public access to Malaysian academic institutions may be of interest. Johari will mail some details to Ridzuan.

 He is evaluating several vendors version of Hadoop 2.0 installations to decide which is the right one to adopt. Last time I successfully install and trying Hadoop 1.0 but then it has many drawbacks such as no real-time streaming processing. He awaits receiving details from Johari about the MYREN cloud.

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/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%20pingER%20big%20data%20with%20a%20modified%20pingtable%20for%20event-correlation%20and%20clustering.docx. He is currently spending  time reading about RDF storage and its retrieval, also he is  trying to setup Hadoop clusters for the experiment. He is in email discussion with Renan on which part to work on first. He plans to  collaborate with Renan to make the pinger store and process more efficient. Les has sent him documentation of PinGER which is very helpful. Ridzuans' work is more to do with hosting the data and stream data analysis. Ibrahim is looking more at applying MapReduce ( programming model for processing large data sets with a paralleldistributed algorithm on a cluster), reducing the storage needs and providing querying of the data.

...

The following nodes (were down for months) and have now been recovered by the efforts made by Kashif in the last two weeks and they are working fine now. These all are also updated with the new beacon list by replacing pinger.xml file.

  1. pinger.lcwunca.edu.pk
  2. pinger.ncanwfpuet.edu.pk
  3. pinger.nwfpuetpern.edu.pk (HEC)
    1. pinger2 command was working on "pinger.pern.edu.pk

    (HEC)
  4. pingerfsbd.pern.edu.pk
  5. pingerisl-fjwu.pern.edu.pk
    1. " but due to space shortage it was not storing data. Now Kashif removed some older files and it starts working again, also the time of the server was not correct so he changed that too.

  6. pingerfsbd.pern.edu.pk
  7. pingerisl-fjwu.pern.edu.pk
  8. pinger.lcwu.edu.pk is also fine. collection status at SLAC will change the color today after collecting data for 19th May arround 4pm PKST. 
  9. pingermtn.pern.edu.pk 
    1. pingermtn.pern.edu.pk remained DOWN for most of the time due to power outage in last week. Due to sudden breakdown, the Linux OS was also creating problem at reboot and get stuck in checkdisk type of errors and was demanding manual clicks and commands.  So, in this situation, Kashif requested to the contact person and he managed to arrange UPS for the PingER monitoring node. Hopefully it will UP now most of the time or at least till the backup time of UPS, if power outage remains for multiple consecutive hours.
  10. pingermtn.pern.edu.pk (node is ok but down again n again due to power outage)pinger.uob.edu.pk is working, but having multi-hour power outages each day. This usually means that when SLAC normally goes to gather the data in the early morning Pacific time the host does not respond so we are unable to gather the data.  Analyzing the outages, it it appears that a good time gather the data is at ~11:00am Pacific time, since the host usually responds at that time.
  11.  www.upesh.edu.pk
  12. buitms.seecs.edu.pk
  13. maggie1.seecs.edu.pk
  14. monitor.seecs.edu.pk

...

...

To assist in SEECS gathering data: getdata.cf is now available via http://www-iepm.slac.stanford.edu/pinger/tools/nodes.cf

...