Changes between Version 38 and Version 39 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-ADM-1
- Timestamp:
- 01/18/13 00:44:18 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-ADM-1
v38 v39 40 40 || 4C || [[Color(green,Pass)]] || 2013-01-17 || || || 41 41 || 4D || [[Color(orange,Blocked)]] || || [instaticket:90] || || 42 || 5A || [[Color( #63B8FF,In Progress)]] |||| || ||43 || 5B || [[Color( #63B8FF,In Progress)]] |||| || ||44 || 5C || [[Color( #63B8FF,In Progress)]] || |||| ||45 || 5D || [[Color( #63B8FF,In Progress)]] |||| || ||42 || 5A || [[Color(green,Pass)]] || 2013-01-17 || || || 43 || 5B || [[Color(green,Pass)]] || 2013-01-17 || || || 44 || 5C || [[Color(orange,Blocked)]] || || [instaticket:91] || || 45 || 5D || [[Color(green,Pass)]] || 2013-01-17 || || || 46 46 || 6A || [[Color(#63B8FF,In Progress)]] || || || || 47 47 || 6B || [[Color(#63B8FF,In Progress)]] || || || || … … 848 848 === Results of testing step 3F: 2012-05-16 === 849 849 850 ''Note: This test was run on the Utah rack." 851 850 852 * pc5 is currently configured as a shared OpenVZ node: it is in the experiment `emulab-ops/shared-nodes` 851 853 * From boss: … … 917 919 === Results of testing step 3G: 2012-05-16 === 918 920 921 ''Note: This test was run on the Utah rack." 922 919 923 * Here's Utah's information about how to use the elabman consoles: 920 924 * The password for the elabman account is in `boss:/usr/testbed/etc/ilo.pswd` … … 1102 1106 1103 1107 === Results of testing step 3H: 2012-05-16 === 1108 1109 ''Note: This test was run on the Utah rack." 1104 1110 1105 1111 * The second prerequisite has not been met (all bare metal nodes are unallocated at this time). To meet it, i will try this via omni: … … 1289 1295 * Each monitored IPs is successfully available at least once 1290 1296 1297 === Results of testing step 5A: 2013-01-17 === 1298 1299 I added a monitored control network ping to control, boss, ops, foam, and flowvisor, and it's working fine; see http://monitor.gpolab.bbn.com/nagios/cgi-bin/status.cgi?host=ilian.gpolab.bbn.com and http://monitor.gpolab.bbn.com/connectivity/instageni.html for example. 1300 1291 1301 === Results of testing step 5A: 2012-05-18 === 1302 1303 ''Note: This test was run on the Utah rack." 1292 1304 1293 1305 ''Note: this is partially blocked, but i want to get a basic ability to detect outages, so am installing what i can.'' … … 1299 1311 === Results of testing step 5A: 2012-07-04 === 1300 1312 1313 ''Note: This test was run on the Utah rack." 1314 1301 1315 * Pings for boss and ops are still operating 1302 1316 * I am adding pings for foam and flowvisor now. … … 1314 1328 * The monitored IP is successfully available at least once 1315 1329 1330 === Results of testing step 5B: 2013-01-17 === 1331 1332 Tim added a BBN InstaGENI sliver to his 'tuptymon' slice for this; the Nagios check is http://monitor.gpolab.bbn.com/nagios/cgi-bin/extinfo.cgi?type=2&host=argos.gpolab.bbn.com&service=ping_instageni-vlan1750.bbn.dataplane.geni.net and http://monitor.gpolab.bbn.com/connectivity/campus.html has a graph. 1333 1316 1334 === Results of testing step 5B: 2012-07-04 === 1335 1336 ''Note: This test was run on the Utah rack." 1317 1337 1318 1338 * Tim added a sliver for monitoring the dataplane subnet yesterday, under slice URN `urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+tuptymon` … … 1329 1349 * I can see general data about all devices in the BBN rack 1330 1350 * I can see detailed information about any services checked 1351 1352 === Results of testing step 5C: 2013-01-17 === 1353 1354 We haven't been told by the InstaGENI team about any monitoring tools, so I created InstaGENI ticket [instaticket:91] to track that. 1331 1355 1332 1356 == Step 5D: GPO receives e-mail about BBN rack alerts == … … 1345 1369 * The duration of the outage 1346 1370 1371 === Results of testing step 5D: 2013-01-17 === 1372 1373 We created three ProtoGENI notification aliases (instageni-ops, instageni-logs, and instageni-stated), and we've been receiving the usual array of ProtoGENI e-mail about them. 1374 1375 We also created a FOAM alias, instageni-foam-admin, and have gotten FOAM-related notifications there. 1376 1377 None of these track outages or rack problems. 1378 1347 1379 === Results of testing step 5D: 2012-07-04 === 1380 1381 ''Note: This test was run on the Utah rack." 1348 1382 1349 1383 * I've been subscribed to `genirack-ops@flux.utah.edu` since 2012-05-24, and have received a number of e-mail messages.