Changes between Version 28 and Version 29 of Gec9ClusterDAgenda


Ignore:
Timestamp:
10/29/10 11:23:07 (9 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Gec9ClusterDAgenda

    v28 v29  
    4747
    4848Task list for Spiral 3: [[BR]]
    49  a Streamline Cluster D site setup and operation, including cluster (Eucalyptus) and connector (L2 switch, with full tag mapping) [[BR]]
    50  b Streamline connectivity to Cluster D sites on campuses, via regional networks (LEARN project) [[BR]]
    51  Allow Cluster D researchers to obtain and stitch resources from multiple Cluster D sites, connected by backbone domain,  using their SM. [[BR]]
    52  Plan to authenticate users in SM via InCommon/Shibboleth  [[BR]]
    53  With other CFs, a plan for consistent names and interfaces [[BR]]
    54  With other CFs, a plan for resource descriptions at interoperability interfaces [[BR]]
    55  Plan to interop with other CFs, particularly from and to protoGENI (Cluster C) [[BR]]
    56  Plan to allow GENI (e.g., protoGENI) researchers to obtain resources via GENI AM API v1.0  (using RSpec resource description) [[BR]]
    57  Plan to allow Cluster D researchers to include tools (e.g., GUSH) to help authorize, reserve, assign and configure resources via “ORCA SM API v1.0” XMLRPC interface to their SM (similar to protoGENI AM API, or possibly same as GENI AM API v2.0) [[BR]]
    58  Plan for Cluster D researchers to get resources from protoGENI aggregates via GENI AM API v1.0 (or possibly protoGENI AM API) (using RSpec resource description) [[BR]]
    59  Plan for naming and stitching L2 connectivity across Cluster C (protoGENI), and Cluster D sites [[BR]]
    60  Plan for operations portal into Cluster D site, including  status and logs, with connections to GMOC [[BR]]
     49 * Streamline Cluster D site setup and operation, including cluster (Eucalyptus) and connector (L2 switch, with full tag mapping) [[BR]]
     50 * Streamline connectivity to Cluster D sites on campuses, via regional networks (LEARN project) [[BR]]
     51 * Plan to allow Cluster D researchers to obtain and stitch resources from multiple Cluster D sites, connected by backbone domain,  using their SM. [[BR]]
     52 * Plan to authenticate users in SM via InCommon/Shibboleth  [[BR]]
     53 * With other CFs, a plan for consistent names and interfaces [[BR]]
     54 * With other CFs, a plan for resource descriptions at interoperability interfaces [[BR]]
     55 * Plan to interop with other CFs, particularly from and to protoGENI (Cluster C) [[BR]]
     56 * Plan to allow GENI (e.g., protoGENI) researchers to obtain resources via GENI AM API v1.0  (using RSpec resource description) [[BR]]
     57 * Plan to allow Cluster D researchers to include tools (e.g., GUSH) to help authorize, reserve, assign and configure resources via “ORCA SM API v1.0” XMLRPC interface to their SM (similar to protoGENI AM API, or possibly same as GENI AM API v2.0) [[BR]]
     58 * Plan for Cluster D researchers to get resources from protoGENI aggregates via GENI AM API v1.0 (or possibly protoGENI AM API) (using RSpec resource description) [[BR]]
     59 * Plan for naming and stitching L2 connectivity across Cluster C (protoGENI), and Cluster D sites [[BR]]
     60 * Plan for operations portal into Cluster D site, including  status and logs, with connections to GMOC [[BR]]
    6161
    6262Demos for GEC10:[[BR]]
    63  Demo experiment where Cluster D researchers obtain and stitch resources from multiple Cluster D sites (and backbone domains) using their SM.[[BR]]
    64  Demo experiment where  protoGENI researchers obtain resources via GENI AM API v1.0, using RSpec resource description.[[BR]]
    65  Demo operations portal into Cluster D site, for status and logs, with connections to GMOC[[BR]]
     63 * Demo experiment where Cluster D researchers obtain and stitch resources from multiple Cluster D sites (and backbone domains) using their SM.[[BR]]
     64 * Demo experiment where  protoGENI researchers obtain resources via GENI AM API v1.0, using RSpec resource description.[[BR]]
     65 * Demo operations portal into Cluster D site, for status and logs, with connections to GMOC[[BR]]
    6666
    6767Demos for GEC11: [[BR]]
    68  Demo experiment where Cluster D researchers get resources from protoGENI aggregates via GENI AM API v1.0  (or possibly protoGENI AM API) (using RSpec resource description)[[BR]]
    69  Demo experiment where Cluster D researchers stitch L2 connectivity across Cluster C (protoGENI), and Cluster D sites[[BR]]
    70  Demo experiment where Cluster D researchers include tools (e.g., GUSH) to help authorize, reserve and assign resources via “ORCA SM API v1.0” XMLRPC interface to their SM (similar to protoGENI AM API, or possibly same as GENI AM API v2.0)[[BR]]
     68 * Demo experiment where Cluster D researchers get resources from protoGENI aggregates via GENI AM API v1.0  (or possibly protoGENI AM API) (using RSpec resource description)[[BR]]
     69 * Demo experiment where Cluster D researchers stitch L2 connectivity across Cluster C (protoGENI), and Cluster D sites[[BR]]
     70 * Demo experiment where Cluster D researchers include tools (e.g., GUSH) to help authorize, reserve and assign resources via “ORCA SM API v1.0” XMLRPC interface to their SM (similar to protoGENI AM API, or possibly same as GENI AM API v2.0)[[BR]]
    7171
    7272[http://groups.geni.net/geni/attachment/wiki/Gec9ClusterDAgenda/Visio-102810_partial_ClusterD_Spiral3_Drawings.pdf  All Figures]: [[BR]]
    7373
    7474 Figure 1-1) and 1-2):  Cluster D Config at end of Spiral 3 [[BR]]
    75  Each Cluster D site is a self-contained aggregate, which can offer resources to all of GENI using GENI AM API.[[BR]]
     75 * Each Cluster D site is a self-contained aggregate, which can offer resources to all of GENI using GENI AM API.[[BR]]
    7676 (See figure below)[[BR]]
    7777
    7878 Figure 2):  ORCA Site Config [[BR]]
    79  Adding interface for Site and GMOC admin/operations[[BR]]
    80  Adding ExpCntrlTools[[BR]]
    81  Adding Measurement Tools (various I&M projects)[[BR]]
    82  Adding UserWorkspaceSrvc and DigitalObjectArchiveSrvc (CNRI project)[[BR]]
     79 * Adding interface for Site and GMOC admin/operations[[BR]]
     80 * Adding ExpCntrlTools[[BR]]
     81 * Adding Measurement Tools (various I&M projects)[[BR]]
     82 * Adding UserWorkspaceSrvc and DigitalObjectArchiveSrvc (CNRI project)[[BR]]
    8383 (See figure below)[[BR]]
    8484
     
    9090
    9191 Figure 4):  ORCA Interop with protGENI [[BR]]
    92  Both from and to protoGENI[[BR]]
    93  Expect to be able to stitch both Cluster D and protoGENI resources[[BR]]
     92 * Both from and to protoGENI[[BR]]
     93 * Expect to be able to stitch both Cluster D and protoGENI resources[[BR]]
    9494 (See figure below)[[BR]]
    9595
    9696 Figure 5):  ORCA Experiment Flow [[BR]]
    97  All steps need to be supported, per I&M architecture[[BR]]
     97 * All steps need to be supported, per I&M architecture[[BR]]
    9898  (See figure below)[[BR]]
    9999
     
    130130
    1311312)  Connectivity planned for Spiral 3:  [[BR]]
    132  Component programming via SSH?  [[BR]]
    133  VLAN connectivity to Internet 2?  NLR?  How many VLANs?   [[BR]]
    134  Ability to control setup of VLANs as part of experiment?   [[BR]]
     132 * Component programming via SSH?  [[BR]]
     133 * VLAN connectivity to Internet 2?  NLR?  How many VLANs?   [[BR]]
     134 * Ability to control setup of VLANs as part of experiment?   [[BR]]
    135135 
    1361363)  Experiments planned for Spiral 3:  [[BR]]
    137  Use by outside researchers?   [[BR]]
    138  Use involving multiple aggregates?  [[BR]]
    139  Use for research experiments?    [[BR]]
     137 * Use by outside researchers?   [[BR]]
     138 * Use involving multiple aggregates?  [[BR]]
     139 * Use for research experiments?    [[BR]]
    140140
    141141=== ORCA/BEN  ===
     
    181181
    182182== Open Discussion (3:30pm) ==
    183 
    184 
     183Who is going to work with the ORCA group on the following tasks? [[BR]]
     184 * Streamline Cluster D site setup and operation, including cluster (Eucalyptus) and connector (L2 switch, with full tag mapping) [[BR]]
     185 * Streamline connectivity to Cluster D sites on campuses, via regional networks (LEARN project) [[BR]]
     186 * Plan to allow Cluster D researchers to obtain and stitch resources from multiple Cluster D sites, connected by backbone domain,  using their SM. [[BR]]
     187 * Plan to authenticate users in SM via InCommon/Shibboleth  [[BR]]
     188 * With other CFs, a plan for consistent names and interfaces [[BR]]
     189 * With other CFs, a plan for resource descriptions at interoperability interfaces [[BR]]
     190 * Plan to interop with other CFs, particularly from and to protoGENI (Cluster C) [[BR]]
     191 * Plan to allow GENI (e.g., protoGENI) researchers to obtain resources via GENI AM API v1.0  (using RSpec resource description) [[BR]]
     192 * Plan to allow Cluster D researchers to include tools (e.g., GUSH) to help authorize, reserve, assign and configure resources via “ORCA SM API v1.0” XMLRPC interface to their SM (similar to protoGENI AM API, or possibly same as GENI AM API v2.0) [[BR]]
     193 * Plan for Cluster D researchers to get resources from protoGENI aggregates via GENI AM API v1.0 (or possibly protoGENI AM API) (using RSpec resource description) [[BR]]
     194 * Plan for naming and stitching L2 connectivity across Cluster C (protoGENI), and Cluster D sites [[BR]]
     195 * Plan for operations portal into Cluster D site, including  status and logs, with connections to GMOC [[BR]]
    185196==  Adjourn (4:00pm)  ==
    186197