Changes between Version 9 and Version 10 of CRON-2Q10-status


Ignore:
Timestamp:
08/24/10 22:11:06 (9 years ago)
Author:
Seung-Jong Park
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CRON-2Q10-status

    v9 v10  
    116116
    117117
    118 *Resolve
    119 *DiscoverResources
    120 *CreateSliver
    121 *DeleteSlice
    122 *GetSliver
    123 *RestartSliver
    124 *RenewSlice
    125 *SliverStatus
    126 *Shutdown
    127 *GetVersion
     118Resolve
     119
     120DiscoverResources
     121
     122CreateSliver
     123
     124DeleteSlice
     125
     126GetSliver
     127
     128RestartSliver
     129
     130RenewSlice
     131
     132SliverStatus
     133
     134Shutdown
     135
     136GetVersion
    128137
    129138Downloaded Emulab-based component manager (https://users.emulab.net/trac/protogeni/wiki/ProtoGENIInstall) , and created our local ProtoGENI domain (http://cron.cct.lsu.edu). Sent out CRON testbed site key certificate to Utah clearinghouse and got confirmed.  Therefore, the CRON component manager could get in touch with Utah clearinghouse. We have not decided to contribute local resources to be registered with Utah clearinghouse.  After data switch development finishes on CRON testbed, we will finish the resource registration and start component manager test on communication with Utah clearinghouse.
     
    133142''' Result log of installation of the Component Manage developed by ProtoGeni(Utah)'''
    134143
    135  /usr/testbed/src/CRON_branch/configure --with-TBDEFS=/usr/testbed/src/CRON_definition_file/defs-CRON-privatecnet
    136 
    137 waiting for Utah clearing house approval
     144/usr/testbed/src/CRON_branch/configure --with-TBDEFS=/usr/testbed/src/CRON_definition_file/defs-CRON-privatecnet
     145
     146####### waiting for Utah clearing house approval #########
    138147
    139148boss# /usr/testbed/sbin/protogeni/initsite