Changes between Version 37 and Version 38 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-ADM-1
- Timestamp:
- 01/17/13 16:34:46 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-ADM-1
v37 v38 34 34 || 3E || [[Color(orange,Blocked)]] || || [instaticket:71] || || 35 35 || 3F || [[Color(green,Pass)]] || 2012-12-20 || || || 36 || 3G || [[Color( orange,Blocked)]] || || [instaticket:72] ||||36 || 3G || [[Color(green,Pass)]] || 2013-01-17 || || [instaticket:72] || 37 37 || 3H || [[Color(green,Pass)]] || 2012-12-20 || || || 38 || 4A || [[Color( #63B8FF,In Progress)]] || |||| ||39 || 4B || [[Color( #63B8FF,In Progress)]] |||| || ||40 || 4C || [[Color( #63B8FF,In Progress)]] |||| || ||41 || 4D || [[Color( #63B8FF,In Progress)]] || |||| ||38 || 4A || [[Color(orange,Blocked)]] || || [instaticket:85] || || 39 || 4B || [[Color(green,Pass)]] || 2013-01-17 || || || 40 || 4C || [[Color(green,Pass)]] || 2013-01-17 || || || 41 || 4D || [[Color(orange,Blocked)]] || || [instaticket:90] || || 42 42 || 5A || [[Color(#63B8FF,In Progress)]] || || || || 43 43 || 5B || [[Color(#63B8FF,In Progress)]] || || || || … … 885 885 * Launching the remote console at each iLO succeeds 886 886 887 === Results of testing step 3G: 2012- 05-16===887 === Results of testing step 3G: 2012-12-20 === 888 888 889 889 I'm not sure why this test only mentions the experiment nodes, and not the control node; I'd think that we'd especially want ILO access to that. … … 912 912 913 913 I was able to SSH to elabman@192.1.242.182, the ILO for pc3, and observe the console in boot wait mode. I reset the system with 'power reset', and that seemed to work. I noted on IG ticket [instaticket:72] that the ILO addresses for the experiment nodes aren't in DNS. 914 915 2013-01-17 update: They've added a page about the ILOs (http://www.protogeni.net/ProtoGeni/wiki/InstaGeni/ILO), closing InstaGENI ticket [instaticket:72], so this is all set. 914 916 915 917 === Results of testing step 3G: 2012-05-16 === … … 1159 1161 }}} 1160 1162 1161 1162 1163 = Step 4: GPO inventories the rack based on our own processes = 1163 1164 … … 1169 1170 * If any objects can't be found in public documentation, compare to internal notes, and iterate with InstaGENI 1170 1171 * Physically label each device in the rack with its name on front and back 1171 * Inventory all hardware details for rack contents on OpsHardwareInventory1172 * Add an ascii rack diagram to OpsHardwareInventory1172 * Inventory all hardware details for rack contents on !OpsHardwareInventory 1173 * Add an ascii rack diagram to !OpsHardwareInventory 1173 1174 1174 1175 '''Verify:''' … … 1177 1178 * We succeed in labelling the devices and adding their hardware details and locations to our inventory 1178 1179 1180 === Results of testing step 4A: 2013-01-17 === 1181 1182 It wasn't obvious to me how to find out the proper names of the things in the rack, so I created InstaGENI ticket [instaticket:85] to find out. 1183 1184 http://groups.geni.net/geni/wiki/GENIRacksHome#InstaGENISpecifications is enough of a "public parts list" for our purposes. 1185 1186 I'd previously added an ASCII rack diagram to !OpsHardwareInventory, and I've now also added the details of the hardware to a table under !OpsHardwareInventory#HardwareforInstaGENIrack. 1187 1179 1188 == Step 4B: Inventory rack power requirements == 1180 1189 1181 1190 '''Using:''' 1182 * Add rack circuit information to OpsPowerConnectionInventory1191 * Add rack circuit information to !OpsPowerConnectionInventory 1183 1192 1184 1193 '''Verify:''' 1185 1194 * We succeed in locating and documenting information about rack power circuits in use 1186 1195 1196 === Results of testing step 4B: 2013-01-17 === 1197 1198 We added this information to !OpsPowerConnectionInventory#InstaGENIrackcircuits on 2012-12-04. 1199 1187 1200 == Step 4C: Inventory rack network connections == 1188 1201 1189 1202 '''Using:''' 1190 * Add all rack ethernet and fiber connections and their VLAN configurations to OpsConnectionInventory1191 * Add static rack OpenFlow datapath information toOpsDpidInventory1203 * Add all rack ethernet and fiber connections and their VLAN configurations to !OpsConnectionInventory 1204 * Add static rack !OpenFlow datapath information to !OpsDpidInventory 1192 1205 1193 1206 '''Verify:''' 1194 1207 * We are able to identify and determine all rack network connections and VLAN configurations 1195 * We are able to determine the OpenFlow configuration of the rack dataplane switch 1208 * We are able to determine the !OpenFlow configuration of the rack dataplane switch 1209 1210 === Results of testing step 4C: 2013-01-17 === 1211 1212 I had VLAN information for procurve1 from step 3E; the VLAN configuration on procurve2 is managed by ProtoGENI. 1213 1214 I was able to log in to procurve2 and show its !OpenFlow information: 1215 1216 {{{ 1217 HP-E5406zl# show openflow 1218 1219 Openflow Configuration 1220 1221 Openflow aggregate VLANs [Disabled] : 1222 Openflow aggregate management VlanId [0] : 0 1223 Openflow second aggregate management VlanId [0] : 0 1224 Openflow aggregate configuration VlanId [0] : 0 1225 1226 VID State HW Active controller Pseudo-URL Conn 1227 ---- ----- --- -------------------------------------------------- ---- 1228 1750 On On tcp:10.3.1.7:6633 Yes 1229 1230 1231 HP-E5406zl# show openflow 1750 1232 1233 Openflow Configuration - VLAN 1750 1234 1235 Openflow state [Disabled] : Enabled 1236 Controller pseudo-URL : tcp:10.3.1.7:6633 * 1237 Listener pseudo-URL : 1238 Openflow software rate limit [100] : 100 1239 Openflow connecting max backoff [60] : 60 1240 Openflow hardware acceleration [Enabled] : Enabled 1241 Openflow hardware rate limit [0] : 0 1242 Openflow hardware stats max refresh rate [0] : 0 1243 Openflow fail-secure [Disabled] : Enabled 1244 Second Controller pseudo-URL : 1245 Third Controller pseudo-URL : 1246 1247 Openflow Status - VLAN 1750 1248 1249 Switch MAC address : 84:34:97:C6:C9:00 1250 Openflow datapath ID : 06D6843497C6C900 1251 Controller connection status (1/1) : connected ; state: ACTIVE 1252 Listening connection status : listening (1 connections) 1253 SW Dpif n_flows: 1 ; cur_capacity:63 ; n_lost: 0 1254 n_hit: 67958 ; n_missed: 984994 ; n_frags: 0 1255 Number of hardware rules: 5 1256 }}} 1257 1258 I added the connection, VLAN, and datapath information to !OpsConnectionInventory and !OpsDpidInventory. 1196 1259 1197 1260 == Step 4D: Verify government property accounting for the rack == … … 1204 1267 * The DD1149 paperwork is complete to BBN government property standards 1205 1268 * We receive a single property tag for the rack, as expected 1269 1270 === Results of testing step 4D: 2013-01-17 === 1271 1272 We have not yet received these forms and tags; I created InstaGENI ticket [instaticket:90] to track that. 1206 1273 1207 1274 = Step 5: Configure operational alerting for the rack =