Versions Compared

Old Version 3

changes.mady.by.user Les Cottrell

Saved on

compared with

New Version Current

changes.mady.by.user Les Cottrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  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): Asif
      1. Document work with AMP integration (hope to complete 11/18/06): Abdullah
      2. Extend to provide perfSONAR data reading front end: 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): Abdullah
      6. Get account (has this been done 11/29/06?): Abdullah
      7. Integrate with pingtable.pl: Abdullah, Jerrod
        1. Create AMP file directory: Jerrod
        2. Set up daily crontab:  Jerrod
        3. Set up analyze-hourly etc: (Done)Jerrod
        4. Add src & dst amp nodes to Guthrie: Jerrod
        5. Think about retrieving older data (find out how long ago there is data for): Jerrod, Adnan
        6. AMP and Pinger data comparison: Abdullah
    2. Smokeping & PingER Integration: Asma, Shahryar
      1. Install at SLAC: Shahryar
        1. Make code available via FTP then Shahryar will download: Asma, Shahryar
        2. Install on test www server: Shahryar, Les
        3. Review code for security and update as neeeded (Shahryar has done and waits Asma updates 2/1/07): Les, Shahryar, Asma
      2. Change from 90 to 120 days - Asma
      3. Look at adding visualization of uptime: Asma
      4. Look at how to dynamically change the config file for Smokeping to accomodate the step interval (maybe time consuming, may affect all users and be cumbersome): Asma
      5. Look at using Smokeping to determine the quality of home links in Pakistan: Asma
      6. Will use as a top level access to PIngER and also as links from Pingtable to display last 45-90 days using smokeping: Asma, Yee
    3. Provide real-time display of PingER data:
      1. Export data to MonALISA from SLAC monitoring site:
      2. Figure how to deal with non regular (non exact 30 min data)
      3. 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. Monitoring Hosts:
      1. NTC hosts, they agreed to install PingER2 at their 3 backbone sites (NTC management has changed, NIIT shifted from NTC to PERN, does not look promising): Arshad, Azher
      2. Pakistan hosts
        1. Wiki Markup-NTC is down since Oct 17th (-{_}{-}NTC management has changed, Arshad will contact upper management 12/4/06{-}{_}{_}-)-_ -\[After talking to NTC does not sound likely this will be restored, 1/11/07\]: Azher, Jerrod-
        2. COMSATS do not ping (Azher reports that COMSATS is very unreliable operation of PingER host): Azher
        3. PERN does not ping and reverse traceroute server is down (need to decide whether to give up on this host and remove it from our list of hosts to use for PingER and TULIP, awaits presentation to PERN/NTC): Azher
        4. PERN would like to provide own archive analysis host (Les has sent URL describing tools needed on archive/analysis host, it maybe that iepm-bw would be more useful to them, or revive the real time PingER plots):

...

  1. Deployment: Faran
    1. Look into Mathematics of Singular Vector Decomposition technique. (agreed 11/16/06): Faran
  2. Improve web page
    1. Need information on the pres file if already running: Faran
    2. Should the tables be able to re-size themselves horizontally?: Faran
  3. Visualization
    1. Make tables sortable (working on 5/25/06, re-agreed 8/3/06, re-requested 8/21/06, done for the RTTs 8/22/06, can we do with buttons for all columns): Faran
    2. Can we add AS's to routes: Yee, Faran
    3. Integrate with Google maps: Faran
    4. When zooming maintain size of dots (there has been no progress on this, should we use Google maps, should we drop it 2/12/07):  Faran
    5. Add landmark response time to Left hand table (Les & Faran are discussing but do not agree 2/12/07)
  4. Landmarks
    1. Get more lanmarks for TULIP:
      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 send email reminder 5/25/06, agreed to send another reminder 6/7/06, Umar will check with Farooq 11/16/06): Faran, Farooq
      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
    2. Add NetDiGi route servers (asked for 8/30/06): Faran
    3. Provide tool to geolocate all PingER sites, analyze results to see what landmarks never respond; Faran
    4. Problem Landmarks:
      1. Enable landmarks that only work for IP addresses (e.g. S. Africa TENET Brunsvigia): Faran
  5. 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
  6. Analysis
    1. Literature search on triangulation, multi-lateration: Faran
    2. Wiki Markup-Measure landmarks from landmarks \ [Done 2/15/07\]: Faran-
    3. Document Faran's algorithm, try new algorithm with optimized alpha that does not require destination to be inside triangle: Faran, Umar
    4. Analyse the effect of passing IP addresses to landmarks rather than names: Faran
    5. Compare with GeoIP Tools
    6. For US compare Faran's algorithm with Octant, GeoLim & 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
  7. Analysis of Accuracy and applicability
    1. Accuracy vs known locations
    2. Effect of removing, adding landmarks, try for Bolivia:Faran
    3. Provide bubble maps of accuracy: Faran
    4. What area/population is covered by TULIP
    5. Document anomalies  (e.g. root-servers): Faran
    6. Show accuracy by region and country: Faran
    7. Come up with a way to estimate the accuracy/confidence of estimates: Faran
      1. Document in the TULIP web page: Faran

...

  1. Get video conferencing working (awaiting echo canelling mike): Azher, Adnan, Les
  2. Projects (see http://www-iepm.slac.stanford.edu/pinger/projects/)
    1. get accounts for Nouman and Fahad: Asif, Shahryar
  3. Visits
    1. The convocation is March 10, 2007
    2. Go over agends: Umar, Les, Adnan
  4. Paper on event diagnosis: Adnan
  5. Case study to S. Asia: Shahryar, Les
    1. When did NIIT switch from NTC to PTCL: Shahryar, Azher
    2. Is Micronet still used: Azher
    3. What do other Univerties in Pak use: Azher
  6. Proposals
    1. Wiki Markup-HEC solicitation for International collaborations, due mid-Sept, Farooq PI (submitted 9/17/06, expect result Dec '06) \ [Our proposal was rejected Jan 07\]-
    2. Get reviews of proposal (done for US, trying Pak thru Atta): Arshad, Les
    3. Submit proposal to HEC (due 2/2/07): Arshad, Umar
    4. Develop new proposal with more a Grid Health viewpoint: Yee, Arshad, Les

...