Tasklist

From MAGGIE

Jump to: navigation, search

The original Task List @ SLAC is to be consulted for all tasks assigned. This task list is to manage local assignments.

Contents

Meeting

NEXT MEETING

  • Thursday 24th April, 2008
    • 9:00 AM California, USA Time,
    • 9:00 PM Islamabad, Pakistan Standard TIme
  • Skype (id: umarkalim) or VRVS video - Room:
  • Contacts: +92-51-9280443 (Dr. Arshad Ali);

Team members

NIIT

Aamir, Ali, Arshad, Fahad, Fida, Nadeem, Noman, Samreen, Shahryar

SLAC

Jared, Les, Qasim, Umar, Yee

Mailing Lists

  • List with all local and international members
    • maggie-niit@googlegroups.com
    • backup: maggie-niit@ns.niit.edu.pk
  • List with all local members (in Pakistan)
    • maggie-local@googlegroups.com
    • backup: maggie-local@ns.niit.edu.pk

Legend

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

Tasks

Communications

  1. AACC paper registration: Shahryar
    1. Camera ready copy has been submitted, registration fees have been paid, waiting for details of date of publication, title of proceedings and online access.
  2. Progress reports of students at NIIT: Umar
    1. Deploy net-weekly: Umar
    2. Communicate the progress to Les & Jared : Umar

TULIP

  1. Analysis
    1. Map TULIPs accuracy by region. This will help in identifying where to add new landmarks : Shahryar
    2. Analyze Speedtest sites with and without PlanetLabs
    3. Study results for North America using all 150 sites, will report results by 03/16/08: Shahryar
      1. Determine which sites have the highest frequency of being selected as one of the top 3 landmarks.
        1. Document the findings
        2. Why isn't SLAC listed in the list of sites?
      2. Observe why some nodes are showing results with errors greater than 1000 Km.
        1. Document the findings
      3. (Data used for analysis should be available to everyone (to allow them to conduct analysis)
      4. Run tests from SLAC or use maggie2
        1. Email Qasim the script and readme so that he may set it up at SLAC: Shahryar
    4. Queries to be answered and documentation of findings: Shahryar - deadline 13/03/08
      1. What values of alpha to use for each tier particularly for N. America & Europe?
        1. Document the findings
      2. Does the alpha value vary with increase in distance between the landmark and the target, how much and why?
        1. Document the findings
      3. Why do the results worsen (in some cases) when using both Planet Lab and PingER nodes?
        1. Document the findings
    5. Evaluate whether using traceroute data helps (Suggested by Umar & Les 2/26/07, could add 3 more RTTs to minimize from):
    6. Comparison of TULIP results with IP2Location, MaxMind, NetGeo, GeoIP, DNSStuff GeoLocation, GeoBytes etc: Shahryar, Samreen
      1. Find cases where TULIP beats GeoIP Tool [Done 4.68.116.16, probably backbone routers too]
      2. Compare with MaxMind (see http://www.maxmind.com/app/geolitecountry)
      3. Document comparison in Wiki
      4. Confidence estimates of accuracy
      5. Applied to PingER hosts
      6. Look at big discrepancies
      7. Provide bubble maps of accuracy: Shahryar
      8. What area/population is covered by TULIP
      9. Show accuracy by region and country
  2. Implementation: Shahryar
    1. Why does TULIP's triangulation algorithm returns longitude and latitude as integers? Can this be fixed? : Shahryar
    2. Add traceroute location:
    3. Add results from GeoIP
    4. Visualization
      1. When zooming maintain size of dots (awaits TULIP2)
    5. Provide API
    6. Publication
      1. Find conference: all
      2. Can we get Cisco interested?: Arshad, Faran
      3. Update documentation: Les
      4. Read paper at http://research.microsoft.com/%7Epadmanab/papers/sigcomm2001.pdf
  3. Bugs/questions (await TULIP2):
    1. How do Sno correlate when there are landmarks from SLAC and PlanetLab. It appears Sno for PlanetLab in Ping Results is not same as Sno in PlanetLab landmarks? (currently it is by order of of appearance in Ping Results 10/2/07):
    2. The alpha optimization using PingER data seems to do nothing useful:
    3. Confidence Estimates table does not sort on table heading (what does it mean, what are units, will replace with IQR/Median 10/2/07):
    4. Location History needs headings or something to explain what the columns are:
    5. Change Ladnmarks to Landmarks on tab in Ping window (reported 9/21/07, will be done in future release 10/2/07):
    6. Sort of LG/SLAC ping results for target = www.cern.ch of sort of Min RTT gives the top entry as 1 (SWITCH,Switzerland), the next is 0.820 (CERN, Geneva), i.e. it has mis-sorted (reported 10/8/07):
    7. PlanetLab ping results table does not sort by table heading (reported 10/8/07):
    8. The alpha test under Discovery Statistics needs to throw away useless values of RTT else plot scaling can be useless:
    9. The alpha optimization using PingER seems to do nothing useful:
    10. South Africa landmark only accepts IP addresses so need to accomodate:
    11. What is fixed vs Min RTT under DiscoveryStatistics (Faran will talk to Asif 10/2/07, not needed now):
    12. Sometimes fails, maybe because when tulip starts it downloads Site.txt from niit server. If that be the case the left side table on the main frame should be empty and status bar should say "Error downloading config. file."
  4. 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
  5. Documentation
    1. Revise thesis documentation and make it available online: Umar

Case Studies

  1. East Asia Case Study: Umar
    1. Gathering of data
    2. Compilation of initial draft see case study

PingER web services

  1. Extend ViPER to turn into front end for PingER, fix bugs and extend to Real Time (see ViPER Extension Details and [Mapping PingER Metrics])
    1. Nauman has a real time version working with ping_data.pl. looks good.
    2. Fix bugs
      1. Still have points in to LH corner
    3. Make JNLP loadable.

IEPM

  1. DB Schema: Fahad
    1. Initial prototype
    2. Revision of schema to include information required by perfSONAR, PingER and TULIP: Jared
    3. Incorporate suggestions made by Jared: Fahad
    4. Stress testing of the data base and documentation of the findings: Fahad - deadline 06/03/08
      1. List all the tables with their schema for the Monitoring node as well as the Archive Server.
      2. List all possible SQL queries that application will use to respond to user queries as shown here [1]
      3. List all possible SQL queries that will be run internally
      4. Run all the queries in a & b to test for correctness
      5. Analyze the performance results
      6. Document your findings
    5. Implementation of the script that aggregates the results
    6. Implementation of the script that transfers the summary & raw data to the archive servers
    7. Deploy the software on maggie2 (archive server) and a prototype monitoring node
    8. Implementation of the scripts triggering tools used by IEPM and consequently parse the results and enter them into the database
    9. Test and deploy the setup at different nodes. Explore the possible scenarios where the setup would include about 60 nodes at various locations in the PERN network.
    10. Devise and implement a scheduler to run tests at appropriate intervals
    11. User interface to view/edit information such as contact details, node description, etc
  2. Traceanal : Qasim
    1. Redesign of Connie work to make it simple
    2. Fix the new version of tracenal, compile a release verion
    3. Remove extra layers from Traceanal i.e. direct connection with database to fetch results
    4. Making separate groups basing on regions and formating html so that relevant data could be added to its group
    5. Using Java Script so to make selection flexible i.e. page displays nodes according to region selected from choice menu.
    6. Script to add all the becons in Traceanal
    7. Script that synchronize IEPM database with PingER NodeDetails database and generate a file of those missing in PingER

Event Detection

  1. Study the distributions of data to see whether they conform to the normal distribution? :Fida, Noman, Umar
  2. If they are not normal, then what distributions to they follow? : Fida, Umar
  3. What are the units of bandwidth measured by IEPM? Why are they different for different tools? : Noman, Umar
  4. Can we have the same solution as that of performance measurement of intra-ASes for inter-ASes? : Noman, Umar
  5. Measurement values for 2007 : Umar
  6. Does this vary with tool, or its always the same for all tools? Fida, Umar
  7. What methods can we use to identify anomalies, using information from these distributions? Fida, Umar
  8. Study the tools (IEPM) to see how they work, what information do they compile? : Noman, Umar

IPEAK

  1. Implement an application that collects statistics such as packet loss, network throughput (estimated), jitter, RTT over:
    1. A TCP connection with an echo server : Towhid
    2. A UDP connection with an echo server : Towhid

Project/Tasks Assigned

  1. End to End Performance Measurement: Fahad
  2. TULIP: Shahryar Khan
  3. Network Event Detection & Diagnosis: Fida
  4. Implementation of Event Detection Algorithms: Noman
  5. Visualization for perfSONAR: Qasim
  6. Implementation of traceanl: Qasim
  7. Novell Certification Exam (deadline 09/03/08): Nadeem
  8. AMP - PingER Integration: Abdullah
  9. Terapaths/Netflow presentation: Ahmad Hassan
  10. Case Study of NIIT's network: Farhan ur Rehman
  11. Visualization for IEPM: Fahad
  12. Landmark Selection: Muniba Malik
  13. Extension of ViPER (PingER Metrics): Nouman Shah
  14. Enhanced visualization for TULIP : Rehan
  15. Realtime access to PingER data: Sameen
Retrieved from "http://maggie2.niit.edu.pk/wiki/index.php/Tasklist"
Personal tools