Changes between Version 32 and Version 33 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-1
- Timestamp:
- 05/23/12 15:07:01 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-1
v32 v33 36 36 || 5B || [[Color(orange,Blocked)]] || || exoticket:28 || Tim is working with ExoGENI to get the vlan 1750 interface setup (exoticket:28) || 37 37 || 5C || [[Color(orange,Blocked)]] || || exoticket:29 || blocked on inquiry about how to determine what command runs a particular check; blocked on resolution of inconsistent site admin nagios access || 38 || 5D || [[Color( orange,Blocked)]] || || || blocked on inquiry about "Check_MK inventory" check||39 || 6A || || || || ready to test||40 || 6B || || || || ready to test||41 || 6C || || || || ready to test||38 || 5D || [[Color(green,Pass)]] || 2012-05-23 || || nagios checks for site admins are quite noisy, but they do work || 39 || 6A || [[Color(green,Pass)]] || 2012-05-23 || || || 40 || 6B || [[Color(green,Pass)]] || 2012-05-23 || || || 41 || 6C || [[Color(#B0E0E6,Complete)]] || || || interim notifications during the test period have been agreed on; revisit longer-term plan for notifications later || 42 42 43 43 == High-level description from test plan == … … 854 854 }}} 855 855 * I don't know what that is and the service page (e.g. [https://bbn-hn.exogeni.net/rack_bbn/check_mk/view.py?view_name=service&site=&service=Check_MK%20inventory&host=bbn-w1.local]) doesn't have a "check manual" defined, but i ''expect'' that what's going on is that there is some code which identifies new VMs and runs Check_MK checks on them, and whenever a new VM comes online or goes away, Check_MK is out of sync for a little while. 856 857 I'll follow up via e-mail to ask about that, and block this in the mean time. 856 * Jonathan verified via e-mail that my guess was correct. 858 857 859 858 == Step 6: Setup contact info and change control procedures == … … 870 869 {{{ 871 870 sudo -u mailman /usr/lib/mailman/bin/find_member -l response-team exogeni-ops 871 }}} 872 873 ==== Results of testing step 6A: 2012-05-23 ==== 874 875 On daulis: 876 {{{ 877 daulis,[~],14:22(0)$ sudo -u mailman /usr/lib/mailman/bin/find_member -l response-team exogeni-ops 878 [sudo] chaos's password on daulis: 879 exogeni-ops@renci.org found in: 880 response-team 872 881 }}} 873 882 … … 884 893 * A new ExoGENI contact has been added 885 894 895 ==== Results of testing step 6B: 2012-05-23 ==== 896 897 I don't have access to GMOC's contact database. Instead, i asked GMOC to verify: 898 * The primary contact e-mail is `exogeni-ops@renci.org` 899 * The secondary contact is a person's e-mail address 900 * There is a phone number associated with one contact 901 Kevin Bohan of GMOC checked and was able to verify these things for me. 902 886 903 === Step 6C: Negotiate an interim change control notification procedure === 887 904 … … 894 911 * ExoGENI agrees to send notifications about planned outages and changes. 895 912 913 ==== Results of testing step 6C: 2012-05-23 ==== 914 915 ExoGENI has agreed to notify exogeni-design or gpo-infra when there are outages. 916 917 We will want to revisit this test when GMOC has workflows in place to handle notifications for rack outages, and before there are additional rack sites and users who may need to be notified.
