You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

PingER: Shahryar, Umar Khan, Les

  1. PingER web services: ?
    1. PingER & AMP Integration (AMP/NLANR has run out of funding, AMP will shut down 8/31/06. Given the demise of AMP this may need to be changed to integration with PerfSONAR, on the other hand it may be useful for converting from the perfSONAT MP/MA format to PingER): Abdullah
      1. Document work with AMP integration (hope to complete 11/18/06, look at using Perldoc): Abdullah
      2. Extend to provide perfSONAR data reading front end (awaits perfSONAR): Abdullah, Asif
      3. Install & integrate code at SLAC: Abdullah
      4. Improve code, make production quality, automate getting data (requested with suggestions 8/20/06, making progress hope to be done in 3-4 days 8/31/06, sent back to SLAC, SLAC responded further formatting etc. improvements needed 9/12/06, we need to either finish this up or say Abdullah is not going to do it 3/20/07, Abdullah agreed to complete and send 3/22/07, Abdullah sent code but it needs indenting and some example documentation mail sent to Abdullah 4/4/07, Abdullah will have the code ready  by 5/3/07, code provided 5/10/07, indentation and commenting need work)
        1. Enable user to specify AMP host an option with a sensible default (has provided 2 files one for local one for dynamic, i.e. go to amp)
        2. Comment what hosts work
        3. Deploy at SLAC
      5. Integrate with pingtable.pl: Abdullah
        1. Create AMP file directory:
        2. Set up daily crontab: 
        3. Add src & dst amp nodes to Guthrie:
        4. AMP and Pinger data comparison: Abdullah
    2. Smokeping & PingER Integration: Shahryar (Asma is no longer working on this)
      1. Install at SLAC: Shahryar
        1. Installation on test www-dev test server : Shahryar, Les
        2. Carried out detail performance analysis of the code. Tried to make the code run faster, by eliminating unecessary instructions. The details of the performance analysis can be found at https://confluence.slac.stanford.edu/display/IEPM/PingER+Smokeping+Integration. We have decide it to run for SLAC only hosts in order to test it for the time being. The results of the analysis shows that it takes 2 hours on average to update all the (536 SLAC to rest of the world RRDs) and will consume approximately 250 MB of disk space.
        3. The generation and presentation of the Smokeping graphs works
      2. Look at adding visualization of uptime (Umar will check with Asma about uptime 4/30/07): Shahryar, Asma
      3. Will use as a top level access to PingER and also as links from Pingtable to display last 120 days using smokeping: Shahryar
      4. Can/should we monitor display uptime (communicating with Asma 5/1/07, Asma answered): Umar, Asma, Shahryar
      5. Need to deploy the code on www-wanmon
    3. Provide real time access to cached data (needs assigning as project)
      1. Do for SLAC
        1. Decide on how to extend to other monitoring sites, try with NIIT:
    4. Ping-data.pl form only shows beacons.
      1. Need to point $sites_fn to pinger.xml instead of beacons.txt & check if the file is xml or flat (for backward compatibility): Shahryar
    5. Case Studies
      1. Case study for E. Asia to be led by Ajou university: Umar

        1. Send China information to Umar [Done 5/10/07]: Les

        2. Send Taiwan information to Umar [Done 5/10/07]: les

        3. Invite Taiwan to be a PingER monitoring host (sent email 5/10/07): Les
    6. Monitoring Hosts:
      1. Pakistan hosts
  • No labels