Changes between Version 26 and Version 27 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-ADM-1
- Timestamp:
- 07/04/12 14:53:37 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-ADM-1
v26 v27 45 45 || 5B || [[Color(yellow,Complete)]] || || || requires re-testing after Utah mesoscale dataplane is connected via UEN; requires re-testing after 1 is completed || 46 46 || 5C || [[Color(red,Fail)]] || 2012-05-27 || || the InstaGENI model does not include a "rack health" high-level UI || 47 || 5D || || || || ready to test at Utah||47 || 5D || [[Color(yellow,Complete)]] || || || requires re-testing after 1 is completed || 48 48 || 6A || [[Color(orange,Blocked-site)]] || || [instaticket:43] || blocked on InstaGENI operators subscribing to response-team || 49 49 || 6B || || || || ready to test || … … 727 727 * The duration of the outage 728 728 729 ==== Results of testing step 5D: 2012-07-04 ==== 730 731 * I've been subscribed to `genirack-ops@flux.utah.edu` since 2012-05-24, and have received a number of e-mail messages. 732 * Most of these messages are notifications of GENI operations 733 * There is also a nightly e-mail, subject "Testbed Audit Results", which reports on the number of experiments which have been swapped in for longer than a day. 734 * There are also notifications of account requests and changes in local projects 735 * This list does not detect and notify about rack problems: InstaGENI does not have a list for that purpose. 736 729 737 == Step 6: Setup contact info and change control procedures == 730 738