Changes between Version 23 and Version 24 of CRON-2Q10-status
- Timestamp:
- 08/25/10 10:55:14 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CRON-2Q10-status
v23 v24 145 145 }}} 146 146 147 PIs have downloaded Emulab-based component manager (https://users.emulab.net/trac/protogeni/wiki/ProtoGENIInstall) , and created our local ProtoGENI domain (http://cron.cct.lsu.edu). Then PIs have 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 the list of local resources to be registered with Utah clearinghouse because a few hardware emulators have a TCL interface problem to the Boss server. After the problem is fixed, PIs will finish the resource registration and start component manager test on communication with Utah clearinghouse.147 PIs have downloaded Emulab-based component manager (https://users.emulab.net/trac/protogeni/wiki/ProtoGENIInstall), and created CRON local ProtoGENI domain (http://cron.cct.lsu.edu). Then PIs have sent out a CRON testbed site key certificate to Utah clearinghouse and got confirmed. Therefore, the CRON component manager could get in touch with Utah clearinghouse after July 2010. We have not decided the list of local resources to be registered with Utah clearinghouse because a few hardware emulators have a TCL interface problem to the Boss server. After the problem is fixed, PIs will finish the resource registration and start component manager test on communication with Utah clearinghouse. 148 148 149 149 Since there have been many ongoing discussions on the component manager among other project participants, PIs plan to finish the development of the component manager before next quarter and test the component manager combining with other federated component manages before next GEC 9 conference.