Maggie-NS Tasklist

NEXT MEETING: 8:00 AM California, USA Time, Tuesday 27th  February, 2007, call 92-51-928-0443

Team members: Abdullah, Adnan*, Arshad, Asma, Azher*, Fahan*, Faran*, Nouman, Umar*

Akbar*, Asif, Les*, Shahryar*, Yee

Mailing lists: maggie-niit@ns.niit.edu.pk; backup: maggie-niit@googlegroups.com

Awaits something, also provides start of wait date
Done or drop, remove < 2 months are task done
: Person doing the work
Bold face: task in progress, or for discussion at meeting
Recent progress/discussion. Need student to be assigned. Critical.

Action Items

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): 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. 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):

Triangulate position of an unknown host (see http://www.slac.stanford.edu/comp/net/wan-mon/tulip,Faran Faran expects to be able to devote more effort to this following 25th Jan 2007): Faran, Les

  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. 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

NETRAT, SLAC contact: Adnan, Les

  1. Evaluate PCA multivariate method of Crovella: Waqar, Adnan,
    1. Compare PCA results with Holt-Winters/plateau: Adnan
      1. Fetch Data From SLAC, BNL, CALTECH (Pathchirp, Thrulay, Ping): Adnan
      2. Fetch data from CERN
      3. Apply PCA on same data and to get potential alerts: Adnan
      4. Comparison of Run-period results and PCA results: Adnan
      5. Improve event detector: Adnan
      6. Docment findings on PCA: Adnan
  2. Forecasting comparison of Active vs. passive data: Fareena, Adnan
    1. Look at eview implementation of ARIMA (QU has copy): Fareena
      1. Extend to more sites/metrics, see need for Integration & higher orders: Farena, Adnan
      2. Try with longer time base: Fareena
      3. Get time estimates : Fareena
    2. Detailed Graphs description: Fareena
    3. Regularization
    4. Look at moodss (http://jfontain.free.fr/statistics.htm): Fareena
    5. Send results/documentation to SLAC (will send 8/31/06): Fareena
    6. Automate procedures
      1. Define project
      2. Put together presentation for workshop (for Sep 2006): Fareena
      3. Gather team
  3. Automatic event isolation: Adnan, Yee
  4. Put together paper for E2E conference Munich Germany in May, due Jan 27th, 2007 (SLAC needs to review paper): Adnan

IEPM data viz

  1. Compress traceanal table - Nouman, Asif
  2. Add node name in RH column
  3. Make nodename clickable to view ping time-series
  4. Add comment or help on how to find the real hostname
  5. Prepare distributable version of traceanal (assign to an NIIT student) - Asif, Yee
  6. Provide ViPER like interface to IEPM data: Fahad, Shahryar
    1. Problem with Google maps, overcome by FTP from remote host: Fahad
    2. Problem with node visibility with FireFox (OK with MSIE 6): Fahad
    3. Deploy at NIIT (done 2/1/07, needs cert): Fahad
    4. Get account at SLAC (Fahad has information 2/15/07); Fahad
    5. Need to understand how to get updates from iepm in real-time (try accessing URL from web browser): Fahad, Shahryar
      1. Formats for ping and traceroute are different (will have to work around): Fahad

Pathneck (see http://maggie.niit.edu.pk/website/projects/Topological_Analysis.html) Yee is the lead at the SLAC end: Asif

  1. Try and get pathneck working from NIIT, study debug output, work with Ningning <hnn@cs.cmu.edu> (awaits site upgrade): Asif
  2. Update production version at SLAC (12/106): Asif, Yee
  3. Develop and install pathneck reverse server (would like to start at NIIT just to assure code works work with -y option): Les, Asif
    1. Modularize security of traceroute.pl: Asif, Yee
    2. Add in PerfSonar: Asif, Yee
  4. Evaluate and understand how pathneck needs to be configured, the failure modes, the areas of applicability etc. using iepm-resp.slac.stanford.edu: Asif
    1. Provide web site documenting failure modes: Asif
  5. Develop a vizualization
    1. Topology (currently with Touchgraph), color links, mouseover ID router, provide snapshot
    2. Click on link/router to get graph
    3. Incorporate location (e.g. via TULIP)
  6. Investigate integration with traceanal and graphviz: Asif
  7. Integrate topology map with pathneck: Asif
  8. Look at using PerfSONAR router information (do not agree well, need to get more statistics, to enable multiple measures need API to get PerfSONAR data, look perfsonar UI): Asif
  9. Try on Ultralight (problems if < 4 hops): Asif
  10. Problem of 0 results (reported to author but not much happening 4/20/06): Asif
  11. Add position and AS information to router database: Asif

Communications etc.

  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. 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

Wiki

  1. Create space for NIIT student reports and populate with initial reports - Yee, Les
  • No labels