Changes between Version 7 and Version 8 of GeniNetworkStitching


Ignore:
Timestamp:
08/09/11 15:53:46 (9 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniNetworkStitching

    v7 v8  
    5050
    5151
     52== GEC11 Network Stitching Engineering Meeting ==
     53
     54Full agenda, summary, and slides for the [wiki:GEC11Stitching GEC11 stitching meeting] are on the wiki. A summary follows.
     55
     56=== Meeting Summary ===
     57'''Tom Lehman''' reviewed the agreed-upon GENI stitching architecture:
     58 - Several functions, to be implemented in various locations or
     59 skipped in certain scenarios :
     60  - Static topology collection
     61  - Path computation
     62  - Workflow/coordination
     63 - A common schema for describing connections between aggregates,
     64 and the capabilities of those connections.
     65 - AM API revisions to support 'chain' (AM to AM) mode, and
     66 negotiation.
     67
     68'''The stitching schema'''
     69 - Based on and interoperable with IDC / OSCARS / perfSonar Topology service
     70 - AMs advertise connection points
     71 - Requests and manifests list hop by hop paths
     72 - http://hpn.east.isi.edu/rspec/ext/stitch/0.1/stitch-schema.xsd
     73 - Follow links in Background Reading for examples and more
     74 information
     75
     76'''Aaron Helsinger''' and '''Chris Benninger''' did a demo of a
     77tree-mode (client-driven) VLAN stitching from ProtoGENI (using the
     78schema) across ION, to MAX. The script calculates dependencies and
     79orders its calls appropriately.
     80
     81'''Tom''' briefly discussed some remaining points to cover
     82 - Negotiation: How do 2 Aggregates negotiation a common stitching
     83 mechanism and configuration? IE, how do they pick a VLAN tag?
     84  - Proposal: an AM API call that reserves a resource without
     85  instantiating it, returning the reserved resource and the other
     86  options that are available
     87 - Chain mode: need an aggregate to aggregate call
     88  - Note authorization issues
     89
     90=== Possible Next steps ===
     91 - Make sample stitching client code available
     92 - Complete schema implementation at ProtoGENI
     93 - Discuss and agree on APIs to support negotiation (eg of VLAN tags)
     94 - Investigate policy considerations in having a real ION Aggregate
     95 Manager
     96 - Prototype topology service based on perfSonar topology service
     97 - Prototype path computation service based on IDC computation service
     98 - Discuss and agree on APIs to support chain/AM-to-AM mode