21 | | || '''Step''' || '''State''' || '''Date completed''' || '''Open Tickets''' || '''Closed Tickets/Comments''' || |
22 | | || 1 || [[Color(green,Pass)]] || 2012-02-24 || || || |
23 | | || 2A || [[Color(orange,Blocked)]] || || exoticket:11 || blocked on a full IP-to-hostname mapping for the subnet || |
24 | | || 2B || [[Color(orange,Blocked)]] || || || blocked on 2A || |
25 | | || 2C || [[Color(orange,Blocked)]] || || || blocked on 2B || |
26 | | || 3A || [[Color(green,Pass)]] || 2012-05-10 || || || |
27 | | || 3B || [[Color(#B0E0E6,Complete)]] || || exoticket:20 || (exoticket:10) [[BR]] access works properly for `xoadmins` members, but not for `bbnadmins` || |
28 | | || 3C || [[Color(green,Pass)]] || 2012-05-10 || || || |
29 | | || 3D || [[Color(green,Pass)]] || 2012-05-11 || || || |
30 | | || 3E || [[Color(orange,Blocked)]] || || || blocked on a working bare metal node implementation (vjo) || |
31 | | || 4A || [[Color(orange,Blocked)]] || || exoticket:22 || need to clarify a couple of inconsistencies in the rack layout diagram || |
32 | | || 4B || [[Color(orange,Blocked)]] || || exoticket:23 || blocked on GPO internal ticket gst:3720, to map from BBN facilities numbering for circuits to IBM's numbering || |
33 | | || 4C || [[Color(#63B8FF,In progress)]] || || || || |
34 | | || 4D || [[Color(orange,Blocked)]] || || exoticket:12 || blocked on government property form || |
35 | | || 5A || [[Color(green,Pass)]] || 2012-05-23 || || || |
36 | | || 5B || [[Color(orange,Blocked)]] || || exoticket:28 || Tim is working with ExoGENI to get the vlan 1750 interface setup (exoticket:28) || |
| 21 | || '''Step''' || '''State''' || '''Date completed''' || '''Open Tickets''' || '''Closed Tickets/Comments''' || |
| 22 | || 1 || [[Color(green,Pass)]] || 2012-02-24 || || || |
| 23 | || 2A || [[Color(orange,Blocked)]] || || exoticket:11 || blocked on a full IP-to-hostname mapping for the subnet || |
| 24 | || 2B || [[Color(orange,Blocked)]] || || || blocked on 2A || |
| 25 | || 2C || [[Color(orange,Blocked)]] || || || blocked on 2B || |
| 26 | || 3A || [[Color(green,Pass)]] || 2012-05-10 || || || |
| 27 | || 3B || [[Color(#B0E0E6,Complete)]] || || exoticket:20 || (exoticket:10) [[BR]] access works properly for `xoadmins` members, but not for `bbnadmins` || |
| 28 | || 3C || [[Color(green,Pass)]] || 2012-05-10 || || || |
| 29 | || 3D || [[Color(green,Pass)]] || 2012-05-11 || || || |
| 30 | || 3E || [[Color(orange,Blocked)]] || || || blocked on a working bare metal node implementation (vjo) || |
| 31 | || 4A || [[Color(orange,Blocked)]] || || exoticket:22 || need to clarify a couple of inconsistencies in the rack layout diagram || |
| 32 | || 4B || [[Color(orange,Blocked)]] || || exoticket:23 || blocked on GPO internal ticket gst:3720, to map from BBN facilities numbering for circuits to IBM's numbering || |
| 33 | || 4C || [[Color(#63B8FF,In progress)]] || || || || |
| 34 | || 4D || [[Color(orange,Blocked)]] || || exoticket:12 || blocked on government property form || |
| 35 | || 5A || [[Color(green,Pass)]] || 2012-05-23 || || || |
| 36 | || 5B || [[Color(orange,Blocked)]] || || exoticket:28 || Tim is working with ExoGENI to get the vlan 1750 interface setup (exoticket:28) || |
| 812 | Item 3: messages related to the `bbn-w1.local` service "Check_MK inventory": |
| 813 | * Approximately twice a day, i've been getting: |
| 814 | * A check_mk inventory warning: |
| 815 | {{{ |
| 816 | From: rack_bbn@bbn-hn.exogeni.net (OMD site rack_bbn) |
| 817 | Date: Wed, 23 May 2012 17:11:32 +0000 |
| 818 | To: chaos@bbn.com |
| 819 | Subject: *** PROBLEM *** bbn-w1.local / Check_MK inventory is WARNING |
| 820 | |
| 821 | --SERVICE-ALERT------------------- |
| 822 | - |
| 823 | - Hostaddress: 10.100.0.11 |
| 824 | - Hostname: bbn-w1.local |
| 825 | - Service: Check_MK inventory |
| 826 | - - - - - - - - - - - - - - - - - |
| 827 | - State: WARNING |
| 828 | - Date: 2012-05-23 17:11:32 |
| 829 | - Output: WARNING - 3 unchecked services (lnx_if:2, qemu:1) |
| 830 | - lnx_if: Interface vnet2 |
| 831 | lnx_if: Interface vnet3 |
| 832 | qemu: VM i-00000556 |
| 833 | |
| 834 | ---------------------------------- |
| 835 | }}} |
| 836 | * A check_mk inventory recovery: |
| 837 | {{{ |
| 838 | From: rack_bbn@bbn-hn.exogeni.net (OMD site rack_bbn) |
| 839 | Date: Wed, 23 May 2012 17:13:32 +0000 |
| 840 | To: chaos@bbn.com |
| 841 | Subject: *** RECOVERY *** bbn-w1.local / Check_MK inventory is OK |
| 842 | |
| 843 | --SERVICE-ALERT------------------- |
| 844 | - |
| 845 | - Hostaddress: 10.100.0.11 |
| 846 | - Hostname: bbn-w1.local |
| 847 | - Service: Check_MK inventory |
| 848 | - - - - - - - - - - - - - - - - - |
| 849 | - State: OK |
| 850 | - Date: 2012-05-23 17:13:32 |
| 851 | - Output: OK - no unchecked services found |
| 852 | - |
| 853 | ---------------------------------- |
| 854 | }}} |
| 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. |
| 858 | |