Versions Compared

Old Version 151

changes.mady.by.user Les Cottrell

Saved on

compared with

New Version 152

changes.mady.by.user Unknown User (shahryar2001)

Saved on

Key

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

...

  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): Abdullah
      2. Extend to provide perfSONAR data reading front end (awaits perfSONAR): Abdullah, Asif
      3. Install & integrate code at SLAC: Abdullah
      4. Working on password protection: Abdullah
      5. 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): Abdullah
        1. Needs to work with -w and strict
        2. Enable user to specify AMP host an option with a sensible default
        3. Comment what hosts work
        4. Deploy at SLAC
      6. Integrate with pingtable.pl: Abdullah
        1. Create AMP file directory:
        2. Set up daily crontab: 
        3. Set up analyze-hourly etc: (Done)Jerrod
        4. Add src & dst amp nodes to Guthrie:
        5. 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. Wiki Markup
          -Needs to set the cron job on a Solaris machine \[Done will use tersk 5/7/07\]: Shahryar, Les-
        3. 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.
        4. The generation and presentation of the Smokeping graphs works
      2. Make documentation point to Asma's detailed reference documentation too: Shahryar Done
      3. Look at adding visualization of uptime (Umar will check with Asma about uptime 4/30/07): Shahryar, Asma
      4. Will use as a top level access to PingER and also as links from Pingtable to display last 120 days using smokeping: Shahryar
      5. Can/should we monitor display uptime (communicating with Asma 5/1/07, Asma answered): Umar, Asma, ShahryarShahryar
      6. Need to deploy the code on www-wanmon
    3. Provide real time access to cached data
      1. Do for SLAC
        1. Decide on how to extend to other monitoring sites, try with NIIT: Akbar, Umer
        2. Hassan is looking into the code sent by Fawad (next step is to get ML web services client to get data): Akbar, Hassan
    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. Monitoring Hosts:
      1. Pakistan hosts
      2. sfsmds2.nsnl.net not responding (sent email 4/12/07, started responding but hostname incorrect, tried to fix now not responding 4/29/07 sent email, following discussion with Warren sent suggestion 5/1/07 by email, probably will need rebuild): Les

...

  1. Deployment: Faran
    1. Look into Mathematics of Singular Vector Decomposition technique. (agreed 11/16/06): Faran
  2. Visualization
    1. Provide documentation (in progress 2/27/07, documented maths of selection 3/20/07, needs updating, agreed to update 3/22/07, should it be a wiki? - Umar thinks good idea need Faran view 4/30/07): Farhan, Faran
    2. Can we add AS's to routes: Yee, Faran
    3. DiscoveryStatistics =>LandMark Analysis need to identify which Site number is displayed (i.e. from which window): Faran
    4. Sites.txt
      1. Add diagnostic to Sites.txt to identify bad formatting: Faran
      2. Allow alpha to change (lot of work, many changes, will improve greatly, changes design, Faran focussing on 4/12/07, need progress)
        1. Look at using PingER historical data to optimize alpha (agreed 4/12/07): Faran
        2. Need a way to display alpha used: Faran
      3. Make project to provide a user interface (e.g. edit) to Sites.txt (Adnan may have a student from his presentation, normalizing students to understand their applicability to task 4/30/07)
    5. When zooming maintain size of dots (Faran will propose to Umar as a student project 4/10/07, he is concerned about the download time, Asif suggests using NASA images for Java platform, will send link 4/12/07):  Faran
  3. Bugs:
    1. Sort on min-RTT is alphabetic, should be numerical (reported 5/3/07): Faran
    2. Double click on line in Ping Results gives web page with wrong landmark.
  4. Evaluate whether using traceroute data helps (Suggested by Umar & Les 2/26/07, could add 3 more RTTs to minimize from): Faran
  5. Landmarks
    1. Get more landmarks for TULIP, ideally need at least one landmark in all major developing countries that do not have direct connections to nearby countries.:
      1. China (sent email to ctsnet 7/26/06, reminded 12/6/06, 1/27/07): Les
      2. Try and get sites in Africa (Les sent email 11/28/06): Les
      3. COMTEC, Japan: Faran
        1. Need to add site to Sites.txt (5/2/07): Faran
      4. Add traceroute/Looking Glass servers in critical areas, if they have a common format (asked for 11/15/06, Les did a manual look at traceroute.org and found about 20 potential landmarks 11/17/06, Faran not clear if one can automate 2/27/07, several are automateable, to prove it Les has added 8, Faran will work on, re-requested 3/26/07 with suggestions): Faran
      5. Get site in Korea at Ajou universitytrying to persuade 5/8/07): Umar
      6. Get site at KHU (server available, problems with permissions to open UDP sockets 5/8/07): Umar
    2. Add NetDiGi route servers (asked for 8/30/06, is able to parse them, will look at adding appropriate hosts 3/22/07): Faran
  6. Apply to PingER node database to check the lat/longs are roughly correct (tried with 300-400 sites but cannnot get results due to fragile Internet at NIIT, will interact with Akbar to make tests at SLAC 8/31/06, exchanged emails on list of PingER hosts to locate 9/3/06): Faran
  7. Analysis
    1. Literature search on triangulation, multi-lateration: Faran
    2. Wiki Markup
      -Measure landmarks from landmarks \[Done 2/15/07\]: Faran-
    3. Optimize alpha by landmark (after have new location algorithm working, will try 1:2 for US, 1:3 for Europe, 2:15 Africa, done at NIIT, need to deploy at SLAC 4/10/07) : Faran
    4. Document Faran's algorithm, try new algorithm that does not require destination to be inside triangle: Faran, Umar
    5. Analyse the effect of passing IP addresses to landmarks rather than names: Faran
    6. Look at impact of increasing number of pings for getting accurate min_RTT (Faran measured for a few sites, Les gave ideas on how to extend and analyze for multiple sites, could be a major project 4/4/07): Faran
    7. Compare with GeoIP Tools
      1. Wiki Markup
        Find a case where TULIP beats GeoIP Tool \[Done 4.68.116.16, probably backbone routers too\]:
    8. For US compare Faran's algorithm with GeoIP & simple triangulation for PingER hosts(in progress 2/1/07)
      1. Confidence estimates
      2. Applied to PingER hosts
      3. Outside triangles, area coverage
      4. Effect/need to vary alpha: Faran
      5. Look at big discrepancies
  8. Analysis of Accuracy and applicability
    1. Accuracy vs known locations (landmarks & PingER hosts): faran
    2. Provide bubble maps of accuracy: Faran
    3. What area/population is covered by TULIP
    4. Show accuracy by region and country: Faran
    5. Come up with a way to estimate the accuracy/confidence of estimates: Faran
      1. Document in the TULIP web page: Faran
  9. Look at publication (helps advance Faran's career and possibly "best project",  will need more analysis)
    1. Find conference: all
    2. Can we get Cisco interested?: Arshad, Faran
    3. Update documentation: Les, Faran
    4. Read paper at http://research.microsoft.com/%7Epadmanab/papers/sigcomm2001.pdf:Image Removed Faran

 Terapaths Yee

...