Changes between Version 3 and Version 4 of CRON-2Q10-status


Ignore:
Timestamp:
08/24/10 20:23:57 (14 years ago)
Author:
Seung-Jong Park
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CRON-2Q10-status

    v3 v4  
    2828
    2929GRI: loni.org-341
     30
    3031status: finished
     32
    3133User:    mazad1
     34
    3235Description: CRON to BBN test1
     36
    3337Start date:7/1/2010
     38
    3439Start time: 14:30
     40
    3541End date: 7/1/2010
     42
    3643End time: 17:00
     44
    3745Bandwidth (Mbps): 100
     46
    3847Source: urn:ogf:network:domain=loni.org:node=lsu-dcn:port=0-2-3:link=*
     48
    3949Destination: urn:ogf:network:domain=dcn.internet2.edu:node=BOST:port=S26879:link=bbn
     50
    4051Source VLAN:3728
     52
    4153Tagged    true
     54
    4255Destination VLAN:3728
     56
    4357Tagged    true
    4458
     
    6276
    6377The circuit information between BBN and Utah is as follows:
    64 site                     IP                      MAC
    65 --------------------------------------------------------------------
     78
     79site                     IP                 MAC
     80
    6681BBN            10.38.28.101         00:0C:29:4A:B0:19
    67 SALT POP    10.38.28.100         00:24:A8:30:A5:00
     82
     83SALT POP       10.38.28.100         00:24:A8:30:A5:00
     84
    6885
    6986Ping data:
    7087
    7188carthage,13:41$ ping 10.38.28.100
     89
    7290PING 10.38.28.100 (10.38.28.100) 56(84) bytes of data.
     91
    739264 bytes from 10.38.28.100: icmp_seq=1 ttl=64 time=118 ms
     93
    749464 bytes from 10.38.28.100: icmp_seq=2 ttl=64 time=58.1 ms
     95
    759664 bytes from 10.38.28.100: icmp_seq=3 ttl=64 time=58.1 ms
    7697
     98
    7799Traceroute data:
    78100
    79101carthage,13:43$ traceroute 10.38.28.100
     102
    80103traceroute to 10.38.28.100 (10.38.28.100), 30 hops max, 40 byte packets
     104
    81105 1  10.38.28.100 (10.38.28.100)  58.244 ms  58.403 ms  58.497 ms
    82106
     107
    83108'''Activity 2'''
     109
    84110To 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.
    85111
    86112In 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).
    87113Inside an Emulab-based component manager proposed by ProtoGeni group (Utah), PIs will support the following APIs:
    88 •       Resolve
     114
     115
     116•       Resolve
     117 
    89118•       DiscoverResources
     119
    90120•       CreateSliver
     121
    91122•       DeleteSlice
     123
    92124•       GetSliver
    93 •       RestartSliver
     125
     126•       RestartSliver
     127 
    94128•       RenewSlice
     129
    95130•       SliverStatus
    96 •       Shutdown
     131
     132•       Shutdown
     133 
    97134•       GetVersion
    98135