Changes between Version 36 and Version 37 of CRON


Ignore:
Timestamp:
01/12/12 10:01:32 (7 years ago)
Author:
Seung-Jong Park
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CRON

    v36 v37  
    134134Federation CRON with PlanetLab@MAX
    135135
    136 For GENI aggregation, at first, a GENI clearinghouse authenticates experimenters and issues them credentials needed to obtain GENI resources for experimentation.  Then GENI aggregates provide resources to experimenters with GENI credentials. A GENI slice holds a collection of computing and communications resources capable of running an experiment or a wide area service. And RSpec is the mechanism for advertising, requesting, and describing the resources used by slice. The Internet2 ION Aggregate Manger does VLAN stitching to connect CRON and MAX as a coherent network. CRON will use the GENI Aggregate Manager API, including Flack and Omni. The GENI Aggregate Manager API provides a common interface to Aggregate Managers, including PlanetLab, ProtoGENI, and OpenFlow. Also, network stitching will be provided for CRON to connect into GENI through Internet2. GENI network stitching operation is to construct a topology of substrates as represented by their Aggregate Managers. Each Aggregate Manager has a unique Rspec which defines its Substrate resources. Rspecs is a topology description of the individual substrate. More technical information is available at CRON wiki (https://wiki.cct.lsu.edu/cronwiki/3._Steps_to_create_slice_using_CRON_and_Planetlab_resources.)
    137 
     136For GENI aggregation, at first, a GENI clearinghouse authenticates experimenters and issues them credentials needed to obtain GENI resources for experimentation.  Then GENI aggregates provide resources to experimenters with GENI credentials. A GENI slice holds a collection of computing and communications resources capable of running an experiment or a wide area service. And RSpec is the mechanism for advertising, requesting, and describing the resources used by slice. The Internet2 ION Aggregate Manger does VLAN stitching to connect CRON and MAX as a coherent network. CRON will use the GENI Aggregate Manager API, including Flack and Omni. The GENI Aggregate Manager API provides a common interface to Aggregate Managers, including PlanetLab, ProtoGENI, and OpenFlow. Also, network stitching will be provided for CRON to connect into GENI through Internet2. GENI network stitching operation is to construct a topology of substrates as represented by their Aggregate Managers. Each Aggregate Manager has a unique Rspec which defines its Substrate resources. Rspecs is a topology description of the individual substrate. More technical information is available at [attachment:1794-IntegratingCRONintoProtoGENI-Report-03Jan-2012.pdf 4Q 2011 Status Report].
    138137[[BR]]
    139138[[Image(CRON:cron_max.png,50%)]][[BR]]