Changes between Version 3 and Version 4 of CRON-2Q10-status
- Timestamp:
- 08/24/10 20:23:57 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CRON-2Q10-status
v3 v4 28 28 29 29 GRI: loni.org-341 30 30 31 status: finished 32 31 33 User: mazad1 34 32 35 Description: CRON to BBN test1 36 33 37 Start date:7/1/2010 38 34 39 Start time: 14:30 40 35 41 End date: 7/1/2010 42 36 43 End time: 17:00 44 37 45 Bandwidth (Mbps): 100 46 38 47 Source: urn:ogf:network:domain=loni.org:node=lsu-dcn:port=0-2-3:link=* 48 39 49 Destination: urn:ogf:network:domain=dcn.internet2.edu:node=BOST:port=S26879:link=bbn 50 40 51 Source VLAN:3728 52 41 53 Tagged true 54 42 55 Destination VLAN:3728 56 43 57 Tagged true 44 58 … … 62 76 63 77 The circuit information between BBN and Utah is as follows: 64 site IP MAC 65 -------------------------------------------------------------------- 78 79 site IP MAC 80 66 81 BBN 10.38.28.101 00:0C:29:4A:B0:19 67 SALT POP 10.38.28.100 00:24:A8:30:A5:00 82 83 SALT POP 10.38.28.100 00:24:A8:30:A5:00 84 68 85 69 86 Ping data: 70 87 71 88 carthage,13:41$ ping 10.38.28.100 89 72 90 PING 10.38.28.100 (10.38.28.100) 56(84) bytes of data. 91 73 92 64 bytes from 10.38.28.100: icmp_seq=1 ttl=64 time=118 ms 93 74 94 64 bytes from 10.38.28.100: icmp_seq=2 ttl=64 time=58.1 ms 95 75 96 64 bytes from 10.38.28.100: icmp_seq=3 ttl=64 time=58.1 ms 76 97 98 77 99 Traceroute data: 78 100 79 101 carthage,13:43$ traceroute 10.38.28.100 102 80 103 traceroute to 10.38.28.100 (10.38.28.100), 30 hops max, 40 byte packets 104 81 105 1 10.38.28.100 (10.38.28.100) 58.244 ms 58.403 ms 58.497 ms 82 106 107 83 108 '''Activity 2''' 109 84 110 To aggregate resources at CRON testbed and share them with other ProtoGeni testbeds, PIs and other collaborators of other ProtoGENI projects have discussed about the component manager. 85 111 86 112 In general, there are two prototypes of component manager, Emulab-based installation and standalone reference model). Since CRON testbed is based on the Emulab software package, PIs will use the Emulab-based component manager (refer http://www.protogeni.net/trac/protogeni/wiki/ComponentManagerAPIV2). 87 113 Inside an Emulab-based component manager proposed by ProtoGeni group (Utah), PIs will support the following APIs: 88 • Resolve 114 115 116 • Resolve 117 89 118 • DiscoverResources 119 90 120 • CreateSliver 121 91 122 • DeleteSlice 123 92 124 • GetSliver 93 • RestartSliver 125 126 • RestartSliver 127 94 128 • RenewSlice 129 95 130 • SliverStatus 96 • Shutdown 131 132 • Shutdown 133 97 134 • GetVersion 98 135