Changes between Initial Version and Version 1 of CRON-2Q10-status


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

--

Legend:

Unmodified
Added
Removed
Modified
  • CRON-2Q10-status

    v1 v1  
     1[[PageOutline]]
     2
     3= CRON Project Status Reports =
     4
     5Period: April 2010 - June 2010
     6
     7== I. Major accomplishments ==
     8
     9=== A. Milestones achieved ===
     101.      Test over a 10Gbps connection between CRON and ProtoGeni nodes
     112.      Develop a component manager at CRON testbed (ongoing discussion among other ProtoGeni project)
     12
     13
     14=== B. Deliverables made ===
     15N/A
     16
     17== II. Description of work performed during last quarter ==
     18
     19=== A. Activities and findings ===
     20During the past quarter, PIs have been working on two issues:
     21(1) network test over a 10Gbps connection  between CRON at LSU and ProtoGeni nodes at BBN and Utah and (2) a component manager which the ProtoGeni (Utah group) has proposed.
     22
     23'''Activity 1'''
     24 After PIs checked two individual connections (LONI to Internet 2 and Internet2 to BBN) through ION service during the first quarter 2010, LONI network administrators changed a web interface to reserve a circuit of Internet2. Therefore, PIs have performed several end-to-end tests between a node inside CRON testbed and a node inside BBN) with a new interface, OSCARS (On demand Secure Circuits and Advance Reservation System), to create a circuit of Internet2. And successfully, they created and performed several connection tests between CRON and BBN nodes with OSCARS.
     25We were able to ping bbn (10.37.28.100) successfully from CRON's machine (ip: 10.37.28.101, mac: 0060.dd46.9e11). But there was a problem with the underlying ION network that was preventing us from building circuits to the Salt Lake PoP from LSU or BBN.  This issue has been corrected and now BBN can ping Utah’s machine. We are trying to explore if ION circuits can be created as multipoint instead of point-to-point. In that case we would be able to test that.
     26
     27The circuit information between LSU to BBN is as follows:
     28
     29GRI: loni.org-341
     30status: finished
     31User:    mazad1
     32Description: CRON to BBN test1
     33Start date:7/1/2010
     34Start time: 14:30
     35End date: 7/1/2010
     36End time: 17:00
     37Bandwidth (Mbps): 100
     38Source: urn:ogf:network:domain=loni.org:node=lsu-dcn:port=0-2-3:link=*
     39Destination: urn:ogf:network:domain=dcn.internet2.edu:node=BOST:port=S26879:link=bbn
     40
     41Source VLAN:3728
     42Tagged    true
     43Destination VLAN:3728
     44Tagged    true
     45
     46Interdomain path
     47
     48urn:ogf:network:domain=loni.org:node=lsu-dcn:port=0-2-3:link=*
     49urn:ogf:network:domain=loni.org:node=lsu-dcn:port=0-2-1:link=*
     50urn:ogf:network:domain=dcn.internet2.edu:node=BATO:port=S27135:link=10.100.90.169
     51urn:ogf:network:domain=dcn.internet2.edu:node=BATO:port=DTL2:link=10.100.90.133
     52urn:ogf:network:domain=dcn.internet2.edu:node=HOUS:port=DTL1:link=10.100.90.134
     53urn:ogf:network:domain=dcn.internet2.edu:node=HOUS:port=DTL2:link=10.100.90.109
     54urn:ogf:network:domain=dcn.internet2.edu:node=KANS:port=DTL2:link=10.100.90.110
     55urn:ogf:network:domain=dcn.internet2.edu:node=KANS:port=DTL1:link=10.100.90.66
     56urn:ogf:network:domain=dcn.internet2.edu:node=CHIC:port=DTL9:link=10.100.90.65
     57urn:ogf:network:domain=dcn.internet2.edu:node=CHIC:port=DTL1:link=10.100.90.62
     58urn:ogf:network:domain=dcn.internet2.edu:node=CLEV:port=DTL9:link=10.100.90.61
     59urn:ogf:network:domain=dcn.internet2.edu:node=CLEV:port=DTL1:link=10.100.90.42
     60urn:ogf:network:domain=dcn.internet2.edu:node=BOST:port=DTL2:link=10.100.90.41
     61urn:ogf:network:domain=dcn.internet2.edu:node=BOST:port=S26879:link=bbn
     62
     63
     64The circuit information between BBN and Utah is as follows:
     65site                     IP                      MAC
     66--------------------------------------------------------------------
     67BBN            10.38.28.101         00:0C:29:4A:B0:19
     68SALT POP    10.38.28.100         00:24:A8:30:A5:00
     69
     70Ping data:
     71
     72carthage,13:41$ ping 10.38.28.100
     73PING 10.38.28.100 (10.38.28.100) 56(84) bytes of data.
     7464 bytes from 10.38.28.100: icmp_seq=1 ttl=64 time=118 ms
     7564 bytes from 10.38.28.100: icmp_seq=2 ttl=64 time=58.1 ms
     7664 bytes from 10.38.28.100: icmp_seq=3 ttl=64 time=58.1 ms
     77
     78Traceroute data:
     79
     80carthage,13:43$ traceroute 10.38.28.100
     81traceroute to 10.38.28.100 (10.38.28.100), 30 hops max, 40 byte packets
     82 1  10.38.28.100 (10.38.28.100)  58.244 ms  58.403 ms  58.497 ms
     83
     84'''Activity 2'''
     85To 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.
     86
     87In 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).
     88Inside an Emulab-based component manager proposed by ProtoGeni group (Utah), PIs will support the following APIs:
     89•       Resolve
     90•       DiscoverResources
     91•       CreateSliver
     92•       DeleteSlice
     93•       GetSliver
     94•       RestartSliver
     95•       RenewSlice
     96•       SliverStatus
     97•       Shutdown
     98•       GetVersion
     99
     100Downloaded 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.
     101
     102Since 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 deploy the component manager before next GEC 9 conference.
     103''' Result of installation of the Component Manage developed by ProtoGeni(Utah)'''
     104// /usr/testbed/src/CRON_branch/configure --with-TBDEFS=/usr/testbed/src/CRON_definition_file/defs-CRON-privatecnet
     105
     106######### waiting for Utah clearing house approval ##############
     107
     108boss# /usr/testbed/sbin/protogeni/initsite
     109Checking for package libxml2>=2.6.26
     110Checking for package p5-Crypt-SSLeay>=0.57
     111Checking for package p5-Frontier-RPC
     112Checking for package p5-XML-LibXML
     113Checking for package xmlsec1
     114No reason to regenerate. Exiting ...
     115Creating Geni pseudo user ...
     116User geniuser/10006 has been created
     117No group membership for geniuser; using the guest group!
     118Creating Geni slices project ...
     119Project GeniSlices/10003 has been created
     120Adding group GeniSlices to local node ...
     121Adding group GeniSlices to ops.cron.cct.lsu.edu.
     122*** /usr/testbed/sbin/mkgroup:
     123    Could not add GeniSlices (6003) to ops.cron.cct.lsu.edu!
     124
     125*** /usr/testbed/sbin/mkproj:
     126    /usr/testbed/sbin/mkgroup GeniSlices failed!
     127*** /usr/testbed/sbin/protogeni/initsite:
     128    Could not approve geni project
     129
     130
     131boss# /usr/testbed/sbin/protogeni/initsite
     132Checking for package libxml2>=2.6.26
     133Checking for package p5-Crypt-SSLeay>=0.57
     134Checking for package p5-Frontier-RPC
     135Checking for package p5-XML-LibXML
     136Checking for package xmlsec1
     137No reason to regenerate. Exiting ...
     138No group membership for [User: geniuser, IDX: 10006]; using the guest group!
     139Generating a 1024 bit RSA private key
     140..............................++++++
     141......++++++
     142writing new private key to 'usercert_key.pem'
     143-----
     144Using configuration from /usr/testbed/lib/ssl/ca.cnf
     145DEBUG[load_index]: unique_subject = "no"
     146Check that the request matches the signature
     147Signature ok
     148The Subject's Distinguished Name is as follows
     149countryName           :PRINTABLE:'US'
     150stateOrProvinceName   :PRINTABLE:'Louisiana'
     151localityName          :PRINTABLE:'Baton Rouge'
     152organizationName      :PRINTABLE:'Louisiana State University'
     153organizationalUnitName:PRINTABLE:'cron.cct.lsu.edu.geniuser'
     154commonName            :PRINTABLE:'a5376850-635a-11df-9f21-002128000a06'
     155emailAddress          :IA5STRING:'geniuser@cron.cct.lsu.edu'
     156Certificate is to be certified until May 19 15:25:10 2011 GMT (365 days)
     157
     158Write out database with 1 new entries
     159Data Base Updated
     160*** /usr/testbed/sbin/mkusercert:
     161    Could not mkdir /users/geniuser/.ssl: No such file or directory
     162*** /usr/testbed/sbin/protogeni/initsite:
     163    Could not create encrypted certificate for geni user
     164
     165
     166boss# /usr/testbed/sbin/protogeni/initsite
     167Checking for package libxml2>=2.6.26
     168Checking for package p5-Crypt-SSLeay>=0.57
     169Checking for package p5-Frontier-RPC
     170Checking for package p5-XML-LibXML
     171Checking for package xmlsec1
     172No reason to regenerate. Exiting ...
     173Creating Databases ...
     174Creating CM certificate ...
     175Creating SA certificate ...
     176Creating SES certificate ...
     177Fetching clearinghouse certificate from Utah ...
     178Getting credential to talk to clearinghouse ...
     179xml response: 500 SSL negotiation failed: error:1406C0C8:SSL routines:GET_SERVER_FINISHED:peer error | error:1406E0C9:SSL routines:GET_SERVER_VERIFY:peer error certificate
     180Content-Type: text/plain
     181Client-Date: Wed, 19 May 2010 15:25:35 GMT
     182Client-Warning: Internal response
     183
     184500 SSL negotiation failed: error:1406C0C8:SSL routines:GET_SERVER_FINISHED:peer error | error:1406E0C9:SSL routines:GET_SERVER_VERIFY:peer error certificate
     185
     186*** /usr/testbed/sbin/protogeni/initsite:
     187    Could not get credential to talk to clearinghouse
     188
     189
     190boss# /usr/testbed/sbin/protogeni/initsite
     191Checking for package libxml2>=2.6.26
     192Checking for package p5-Crypt-SSLeay>=0.57
     193Checking for package p5-Frontier-RPC
     194Checking for package p5-XML-LibXML
     195Checking for package xmlsec1
     196No reason to regenerate. Exiting ...
     197Creating Databases ...
     198Fetching clearinghouse certificate from Utah ...
     199Getting credential to talk to clearinghouse ...
     200xml response: 500 SSL negotiation failed: error:1406C0C8:SSL routines:GET_SERVER_FINISHED:peer error | error:1406E0C9:SSL routines:GET_SERVER_VERIFY:peer error certificate
     201Content-Type: text/plain
     202Client-Date: Wed, 19 May 2010 15:25:54 GMT
     203Client-Warning: Internal response
     204
     205500 SSL negotiation failed: error:1406C0C8:SSL routines:GET_SERVER_FINISHED:peer error | error:1406E0C9:SSL routines:GET_SERVER_VERIFY:peer error certificate
     206
     207*** /usr/testbed/sbin/protogeni/initsite:
     208    Could not get credential to talk to clearinghouse
     209
     210
     211$$$$$$$ after Utah confirmed, everything looks fine $$$$$$$$$
     212boss# /usr/testbed/sbin/protogeni/initsite
     213Checking for package libxml2>=2.6.26
     214Checking for package p5-Crypt-SSLeay>=0.57
     215Checking for package p5-Frontier-RPC
     216Checking for package p5-XML-LibXML
     217Checking for package xmlsec1
     218No reason to regenerate. Exiting ...
     219Files /usr/testbed/etc/genica.bundle and /tmp/genica.bundle.66532 differ
     220Stopping apache.
     221Waiting for PIDS: 64582.
     222Starting apache.
     223Creating Databases ...
     224Fetching clearinghouse certificate from Utah ...
     225Getting credential to talk to clearinghouse ...
     226Registering SA cert at the clearinghouse.
     227Registering CM cert at the clearinghouse.
     228Registering SES cert at the clearinghouse.   //
     229
     230=== B. Project participants ===
     231
     232*Seung-Jong Park, PI
     233*Rajgopal Kannan, co-PI
     234*Cheng Cui, graduate student
     235*Mohammed Azad, graduate student
     236*Lin Xue, graduate student
     237
     238=== C. Publications (individual and organizational) ===
     239N/A