Changes between Version 14 and Version 15 of GEC10Stitching


Ignore:
Timestamp:
04/04/11 14:50:29 (8 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC10Stitching

    v14 v15  
    6565=== Next steps ===
    6666 - Schema: Jon Duerig of ProtoGENI is iterating on a PG-compatible stitching schema that preserves ION compatibility.
    67  - Functions: The community will continue discussion points as described below, particularly working out how chain & tree interoperate, and working though some use cases.
     67 - Functions: The community will continue discussing key points, particularly working out how chain & tree interoperate, and working though some use cases.
    6868 - API to be proposed for adoption at GEC11
    6969 - Interoperability demonstration at GEC12
    7070
    71 === Selected points from the discussions ===
    72  - Don't make use of all functions mandatory
     71=== Selected points from the discussion ===
     72 - Don't make use of all functions mandatory.
    7373 - Functions are not necessarily new architectural boxes
    74  - Tom suggested some functions could have an implementation which exists as a central GENI service (eg Topology Service), available to all for use as desired.  Although use would not required.
     74 - Tom suggested some functions could have an implementation which exists as a central GENI service (eg Topology Service), available to all for use as desired.  Although use would not be required.
    7575 - The architecture should not force CFs to redo work they've already done
    7676 - We must support both chain and tree workflows
    77   - can they work together? Is 1 a subset of the other, modulo security?
    78  - How much direct negotiation between aggregates is required: this adds complexity, but without VLAN translation may be necessary
     77  - Can they work together? Is 1 a subset of the other, modulo security?
     78 - How much direct negotiation between aggregates is required? This adds complexity, but without VLAN translation may be necessary.
    7979 - How prevalent should we expect translation to be? do we optimize for it?
    8080 - Work out some use cases. For example, make sure a large topology that loops back (A -> B -> A) is explicitly worked through as an example and supported.