Changes between Version 2 and Version 3 of ProjTemp-Post-GEC10-status


Ignore:
Timestamp:
03/31/11 22:11:25 (8 years ago)
Author:
Don Kline
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjTemp-Post-GEC10-status

    v2 v3  
    1818
    1919(02/18/11) Selection of Alaska resources to be federated with GENI.
    20         Documented the federation options and described new capabilities these resources would bring to GENI.
     20    * Documented the federation options and described new capabilities these resources would bring to GENI.
    2121
    2222(03/16/11) VMI technology consistent with GENI I&M Architecture.
    23         Highlighted how VMI fits into the current version of the I&M system diagram.
    24         Instrumentation/measurement data from VMI now conforms to PerfSONAR schema for measurement data.
     23    * Highlighted how VMI fits into the current version of the I&M system diagram.
     24    * Instrumentation/measurement data from VMI now conforms to PerfSONAR schema for measurement data.
    2525
    2626(Due 03/18/11) Demonstration and outreach at GEC10
    27         Promoted the use of VMI technology on ORCA.[[BR]]
    28         Demonstrated VMI that included I&M/PerfSONAR compliant output (Actual demo moved to April 4, 2011).
     27    * Promoted the use of VMI technology on ORCA.[[BR]]
     28    * Demonstrated VMI that included I&M/PerfSONAR compliant output (Actual demo moved to April 4, 2011).
    2929
    3030
     
    3434
    3535We have selected resources in Alaska to become a distributed ORCA installation. These include server(s) at:
    36         The computer science department at UAF[[BR]]
    37         The UAF datacenter[[BR]]
    38         Bristol Bay campus in Dillingham, Alaska[[BR]]
    39         Ketchikan, Alaska campus[[BR]]
     36    * The computer science department at UAF[[BR]]
     37    * The UAF datacenter[[BR]]
     38    * Bristol Bay campus in Dillingham, Alaska[[BR]]
     39    * Ketchikan, Alaska campus[[BR]]
    4040
    4141Two of these locations have been changed at the request of the IT staff here at UA.  They preferred Barrow and Kotzebue to Ketchikan and Dillingham since these locations would provide a better environment for the initial deployments of experimental equipment i.e. it provided a more reliable phased federation. These locations will still provide high latency satellite links to experimenters, as stated in the resource selection document for out teams February 15th deliverable.
     
    4444
    4545A classification schema very similar to the one described in the Model Federation Framework documentation has undergone significant development. This schema is intended to store the high-level resource descriptions of the University of Alaska (UA) clearinghouse.
    46         This includes a data dictionary used for validating high-level resource descriptions saved into the UA clearinghouse.[[BR]]
    47         The data dictionary has a management and public interface mostly complete.[[BR]]
    48         The clearinghouse has a management interface mostly complete.
     46    * This includes a data dictionary used for validating high-level resource descriptions saved into the UA clearinghouse.[[BR]]
     47    * The data dictionary has a management and public interface mostly complete.[[BR]]
     48    * The clearinghouse has a management interface mostly complete.
    4949
    5050=== B. Project participants ===