Changes between Version 45 and Version 46 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-5
- Timestamp:
- 01/15/13 16:04:03 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-5
v45 v46 4 4 This page captures status for the test case IG-EXP-5, which verifies the ability to support !OpenFlow operations and integration with meso-scale compute resources and other compute resources external to the InstaGENI rack. For overall status see the [wiki:GENIRacksHome/InstageniRacks/AcceptanceTestStatus InstaGENI Acceptance Test Status] page. 5 5 6 ''Last Update: 10/04/12''6 ''Last Update: 2013/01/15'' 7 7 8 8 = Test Status = … … 11 11 12 12 || '''Step''' || '''State''' ||''' Ticket ''' || '''Comments''' || 13 || Step 1 ||[[Color(yellow,Complete)]] || || Experiment modified to use Utah rack||13 || Step 1 ||[[Color(yellow,Complete)]] || || || 14 14 || Step 2 ||[[Color(yellow,Complete)]] || || || 15 15 || Step 3 ||[[Color(yellow,Complete)]] || || || … … 56 56 = Test Plan Steps = 57 57 58 This procedure are executed at Utah InstaGENI, not as originally planned at BBN additionally, due to rack delivery delays.59 Additionally, the initial run through for this procedure is also modified to use one set of user credentials, running two slices for one experiment. 58 This procedure is executed at GPO InstaGENI and it uses three set of credentials to setup 3 separate experiments. The PG Utah aggregate is used to reserve two WAPG nodes, one at Rutgers (Internet2) and one at Indiana (NLR). 59 60 60 61 61 The following aggregate managers nick_names are define in the omni_config used for this test: 62 62 63 63 {{{ 64 ig-utah=,http://utah.geniracks.net/protogeni/xmlrpc/am 65 pg=,http://www.emulab.net/protogeni/xmlrpc/am 66 pg2=,https://www.emulab.net:12369/protogeni/xmlrpc/am/2.0 67 of-bbn=,https://foam.gpolab.bbn.com:3626/foam/gapi/1 68 of-clemson=,https://foam.clemson.edu:3626/foam/gapi/1 64 ig-utah=,http://utah.geniracks.net/protogeni/xmlrpc/am/2.0 65 of-ig=,https://foam.utah.geniracks.net:3626/foam/gapi/1 66 pg-utah=,https://www.emulab.net:12369/protogeni/xmlrpc/am/2.0 67 pg-gpo=,https://pgeni.gpolab.bbn.com/protogeni/xmlrpc/am/2.0 # WAPG nodes 68 69 70 #OpenFlow Aggregates 71 ig-of-gpo=,https://foam.instageni.gpolab.bbn.com:3626/foam/gapi/1 #GPO IG 72 of-gpo=,https://foam.gpolab.bbn.com:3626/foam/gapi/1 #GPO Site 73 of-nlr=,https://foam.nlr.net:3626/foam/gapi/1 69 74 of-i2=,https://foam.net.internet2.edu:3626/foam/gapi/1 70 of-ig=,https://foam.utah.geniracks.net:3626/foam/gapi/1 71 of-uen=,https://foamyflow.chpc.utah.edu:3626/foam/gapi/1 75 of-indiana=,https://foam.noc.iu.edu:3626/foam/gapi/1 72 76 of-rutgers=,https://nox.orbit-lab.org:3626/foam/gapi/1 73 plc-bbn=,http://myplc.gpolab.bbn.com:12346/74 plc-clemson=,http://myplc.clemson.edu:12346/75 77 }}} 76 78 77 79 == 1. As Experimenter1 (lnevers@bbn.com), determine PG site compute resources and define RSpec == 78 80 79 Collect list resources from InstaGENI compute and network aggregate managers. 80 {{{ 81 $ omni.py -a ig-utah listresources -o 82 $ omni.py -a pg listresources -o 83 $ omni.py -a of-ig listresources -V1 -o 81 Collect list resources from InstaGENI compute and network aggregate managers for the first experiment: 82 {{{ 83 $ omni.py -a ig-gpo listresources -o 84 $ omni.py -a ig-of-gpo listresources -V1 -o 84 85 $ omni.py -a of-i2 listresources -V1 -o 85 }}} 86 87 Defined the [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-pg-site.rspec IG-EXP-5-exp1-pg-site.rspec] file to request the ProtoGENI site compute resources request. 88 89 90 == 2. Determine remote meso-scale compute resources and define RSpec == 91 92 The RSpecs for experiment 1 are defined for the meso-scale sites at Rutgers, where one WAPG node (pg51) is used via Internet2. Note, WAPG node pg51 stopped appearing in the listresources output for Emulab in early August. This was reported, but never resolved. 93 86 $ omni.py -a of-nlr listresources -V1 -o 87 $ omni.py -a of-rutgers listresources -V1 -o 88 }}} 89 90 91 == 2. Determine remote Meso-scale compute resources and define RSpec == 92 93 For Experiment1, a Rutgers WAPG node is used as a remote Meso-scale. RSpecs were defined for Rutgers FOAM aggregate and WAPG compute resource. The following RSpec is used for the Rutgers Meso-scale site: 94 95 * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-rutgers-wapg.rspec IG-EXP-5-exp1-rutgers-wapg.rspec] - Rutgers WAPG nodes pg51 compute resource request RSpec. 94 96 95 97 == 3. Define a request RSpec for !OpenFlow network resources at the InstaGENI AM == 96 98 97 Defined the RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-openflow-ig.rspec IG-EXP-5-exp1-openflow-ig.rspec] for the Utah InstaGENI FOAM Aggregate to allow the site PG site compute resources to access the core VLAN 3716. 99 GPO campus resources RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-openflow-ig-gpo.rspec IG-EXP-5-exp1-openflow-ig-gpo.rspec] which access the !OpenFlow VLAN 1750 via the InstaGENI !OpenFlow switch in the GPO InstaGENI Rack. 100 101 The InstaGENI Rack access the backbone via the GPO OpenFlow Switch, which require a separate request to the GPO Site FOAM [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-openflow-gpo.rspec IG-EXP-5-exp1-openflow-gpo.rspec]. 98 102 99 103 == 4. Define a request RSpec for !OpenFlow network resources at the remote I2 Meso-scale site == 100 104 101 RSpecs were defined for Rutgers FOAM aggregate and WAPG compute resource. The following RSpecs were used for the meso-scale site: 102 103 * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-rutgers-wapg.rspec IG-EXP-5-exp1-rutgers-wapg.rspec] - Rutgers WAPG nodes pg51 compute resource request RSpec. 105 The following RSpec is used for the Rutgers FOAM Aggregate: 104 106 105 107 * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-openflow-rutgers.rspec IG-EXP-5-exp1-openflow-rutgers.rspec] - Rutgers FOAM Aggregate network resource request RSpec. 106 108 109 107 110 == 5. Define a request RSpec for the !OpenFlow Core resources == 108 111 109 The file [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-openflow-i2.rspec IG-EXP-5-exp1-openflow-i2.rspec] defines the Internet2 Core FOAM Aggregate network resources request RSpec. 112 The RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-openflow-i2.rspec IG-EXP-5-exp1-openflow-i2.rspec] defines the Internet2 Core FOAM Aggregate network resources request. 113 114 The RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-openflow-nlr.rspec IG-EXP-5-exp1-openflow-nlr.rspec] defines the NLR Core FOAM Aggregate network resources request. 115 110 116 111 117 == 6. Create the first slice == 112 118 113 Created the first slice as with GPO ProtoGENI credentials :119 Created the first slice as with GPO ProtoGENI credentials lnevers@bbn.com: 114 120 {{{ 115 121 $ omni.py createslice IG-EXP-5-exp1 116 122 }}} 117 == 7. Create a sliver for the BBNcompute resources ==118 119 Created slivers at the PG Utah compute resource aggregate123 == 7. Create a sliver for the GPO compute resources == 124 125 The compute resources at the BBN campus only require a FOAM request to allow the connections though the !OpenFlow switch in the InstaGENI rack. 120 126 121 127 {{{ 122 $ omni.py -a pg createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-pg-site.rspec128 $ omni.py -a of-gpo createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-openflow-gpo.rspec -V1 123 129 }}} 124 130 125 131 == 8. Create a sliver at the I2 meso-scale site using FOAM at site == 132 126 133 Created a sliver at the Rutgers FOAM for VLAN 3716: 127 134 {{{ … … 129 136 }}} 130 137 131 == 9. Create a sliver at of the UtahInstaGENI AM ==132 133 Created slivers at the InstaGENI rack FOAM network resource aggregate and at the UEN Regional:134 135 {{{ 136 $ omni.py -a of-ig createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-openflow-ig.rspec -V1137 $ omni.py -a of-uen createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-openflow-uen.rspec -V1 138 }}} 138 == 9. Create a sliver at of the GPO InstaGENI AM == 139 140 The GPO InstaGENI FOAM requires a sliver to allow the InstaGENI campus traffic to the core: 141 142 {{{ 143 $ omni.py -a ig-of-gpo createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-openflow-ig-gpo.rspec -V1 144 }}} 145 139 146 140 147 == 10. Create a sliver for the !OpenFlow resources in the core == … … 143 150 {{{ 144 151 $ omni.py -a of-i2 createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-openflow-i2.rspec -V1 152 $ omni.py -a of-nlr createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-openflow-nlr.rspec -V1 153 145 154 }}} 146 155 147 156 == 10a. Create a sliver for all remaining Meso-scale compute and network resources == 148 157 149 WAPG nodes are part of the Utah PG aggregate, therefore a second request to add a resource does not work. Also modify sliver is not an available feature at this time, so this step is modified to create a second slice for experiment1. In order to create a second request at the PG site the following slice and sliver were created for the Rutgers WAPG node: 150 {{{ 151 $ omni.py createslice IG-EXP-5-exp1a 152 $ omni.py -a pg2 createsliver IG-EXP-5-exp1a --api-version 2 -t GENI 3 IG-EXP-5-exp1-rutgers-wapg.rspec 158 WAPG nodes are part of the Utah PG aggregate, created a sliver at the PG site to request the Rutgers WAPG node: 159 {{{ 160 $ omni.py -a pg createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-rutgers-wapg.rspec 153 161 }}} 154 162 … … 156 164 Verify that all slivers are ready: 157 165 {{{ 166 $ omni.py -a ig-of-gpo sliverstatus IG-EXP-5-exp1 -V1 167 $ omni.py -a of-gpo sliverstatus IG-EXP-5-exp1 -V1 168 $ omni.py -a of-i2 sliverstatus IG-EXP-5-exp1 -V1 169 $ omni.py -a of-nlr sliverstatus IG-EXP-5-exp1 -V1 170 $ omni.py -a of-rutgers sliverstatus IG-EXP-5-exp1 -V1 158 171 $ omni.py -a pg sliverstatus IG-EXP-5-exp1 159 $ omni.py -a of-rutgers sliverstatus IG-EXP-5-exp1 -V1 160 $ omni.py -a of-ig sliverstatus IG-EXP-5-exp1 -V1 161 $ omni.py -a of-i2 sliverstatus IG-EXP-5-exp1 -V1 162 $ omni.py -a pg2 sliverstatus IG-EXP-5-exp1a 163 }}} 164 When all slivers are ready, determine which nodes are assigned for compute resources: 165 {{{ 166 $ omni.py -a pg sliverstatus IG-EXP-5-exp1 -o 167 $ omni.py -a pg2 sliverstatus IG-EXP-5-exp1a --api-version 2 -t GENI 3 -o 168 }}} 169 The above created output files from which the assigned hosts can be determined: 170 {{{ 171 $ egrep "hostname" IG-EXP-5-sliverstatus-SITENAME.json 172 }}} 173 Or you me also use the gcf/examples/readyToLogin.py script: 174 {{{ 175 $ ./examples/readyToLogin.py -a pg IG-EXP-5-exp1 176 ... 177 ================================================================================ 178 Aggregate [http://www.emulab.net/protogeni/xmlrpc/am] has a ProtoGENI sliver. 179 180 pc444.emulab.net's geni_status is: ready 181 Login using: 182 xterm -e ssh -i ~/.ssh/id_rsa lnevers@pc444.emulab.net -p 31802 & 183 ================================================================================ 184 }}} 185 186 187 And for the Rutgers WAPG node: 188 {{{ 189 $ ./examples/readyToLogin.py -a pg2 IG-EXP-5-exp1a -V2 190 ================================================================================ 191 Aggregate [https://www.emulab.net:12369/protogeni/xmlrpc/am/2.0] has a ProtoGENI sliver. 192 193 pg51.emulab.net's geni_status is: ready 194 Login using: 195 xterm -e ssh -i ~/.ssh/id_rsa lnevers@pg51.emulab.net & 196 ================================================================================ 172 }}} 173 The site campus resource are not allocated by the InstaGENI Compute resource aggregate, therefore they are setup before the experiment to have interfaces on VLAN 1750 via a port on the GPO InstaGENI Switch. 174 175 When all slivers are ready, determine login for Rutgers nodes: 176 {{{ 177 178 $ readyToLogin.py -a pg IG-EXP-5-exp1 179 197 180 }}} 198 181 199 182 == 12. Verify that traffic is delivered to target == 200 183 201 Logged in with the following: 202 {{{ 203 $ ssh lnevers@pc444.emulab.net -p 31802 & 204 }}} 205 206 Exchanged traffic with the remote meso-scale resource at Rutgers: 184 Exchanged traffic from the remote meso-scale resource at Rutgers to the GPO campus resource siovale: 207 185 {{{ 208 186 $ ssh lnevers@pg51.emulab.net