Changes between Version 9 and Version 10 of CRON-2Q10-status
- Timestamp:
- 08/24/10 22:11:06 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CRON-2Q10-status
v9 v10 116 116 117 117 118 *Resolve 119 *DiscoverResources 120 *CreateSliver 121 *DeleteSlice 122 *GetSliver 123 *RestartSliver 124 *RenewSlice 125 *SliverStatus 126 *Shutdown 127 *GetVersion 118 Resolve 119 120 DiscoverResources 121 122 CreateSliver 123 124 DeleteSlice 125 126 GetSliver 127 128 RestartSliver 129 130 RenewSlice 131 132 SliverStatus 133 134 Shutdown 135 136 GetVersion 128 137 129 138 Downloaded 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. … … 133 142 ''' Result log of installation of the Component Manage developed by ProtoGeni(Utah)''' 134 143 135 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 ######### 138 147 139 148 boss# /usr/testbed/sbin/protogeni/initsite