Changes between Version 12 and Version 13 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-1


Ignore:
Timestamp:
05/10/12 12:36:55 (8 years ago)
Author:
chaos@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-1

    v12 v13  
    2626|| 3A         || [[Color(green,Pass)]]       || 2012-05-10           ||                    ||                                                                                      ||
    2727|| 3B         || [[Color(#B0E0E6,Complete)]] ||                      || exoticket:20       || (exoticket:10) [[BR]] access works properly for `xoadmins` members, but not for `bbnadmins` ||
    28 || 3C         ||                             ||                      ||                    || ready to test                                                                        ||
     28|| 3C         || [[Color(#63B8FF,In progress)]] ||                      ||                    || still need to verify that `bbn-w4` is not running !OpenStack right now ||
    2929|| 3D         ||                             ||                      ||                    || ready to test                                                                        ||
    3030|| 3E         || [[Color(orange,Blocked)]]   ||                      ||                    || blocked on a working bare metal node implementation (vjo)                            ||
     
    250250 * For each connection, either the connection succeeds or we can verify that the node is not an !OpenStack worker.
    251251
     252==== Results of testing: 2012-05-10 ====
     253
     254 * According to `/etc/hosts`:
     255{{{
     25610.100.0.11             bbn-w1.local            bbn-w1
     25710.100.0.12             bbn-w2.local            bbn-w2
     25810.100.0.13             bbn-w3.local            bbn-w3
     25910.100.0.14             bbn-w4.local            bbn-w4
     260}}}
     261 So i think the names `bbn-w[1-4]` will point to the VLAN 1007 (!OpenStack) locations.
     262 * Chaos's login from `bbn-hn` to `bbn-w1` using public-key SSH:
     263{{{
     264bbn-hn,[~],16:18(0)$ ssh bbn-w1
     265Last login: Fri Apr 27 12:27:02 2012 from bbn-hn.local
     266...
     267bbn-w1,[~],16:19(0)$ sudo whoami
     268[sudo] password for chaos:
     269root
     270}}}
     271 * Tim reported successful login from `bbn-hn` to `bbn-w1` and was able to sudo, so this works for members of the `bbnadmins` group as well.
     272 * Chaos's login from `bbn-hn` to `bbn-w2`:
     273{{{
     274bbn-hn,[~],16:25(0)$ ssh bbn-w2
     275Last login: Fri Mar 23 20:09:42 2012 from bbn-hn.bbn.exogeni.net
     276...
     277bbn-w2,[~],16:25(0)$ sudo whoami
     278[sudo] password for chaos:
     279root
     280}}}
     281 * Chaos's login from `bbn-hn` to `bbn-w3`:
     282{{{
     283bbn-hn,[~],16:26(0)$ ssh bbn-w3
     284Last login: Fri Mar 23 20:14:17 2012 from bbn-hn.bbn.exogeni.net
     285...
     286bbn-w3,[~],16:26(0)$ sudo whoami
     287[sudo] password for chaos:
     288root
     289}}}
     290 * Chaos's login from `bbn-hn` to `bbn-w4`:
     291{{{
     292bbn-hn,[~],16:27(0)$ ssh bbn-w4
     293ssh: connect to host bbn-w4 port 22: No route to host
     294}}}
     295 I need to verify that `bbn-w4` is inaccessible because it is not running !OpenStack, rather than because something else is amiss.  Two possible ways i could verify this:
     296   * I can look at the IPMI console when i get to that point, and verify that the node's console appears to be doing something other than !OpenStack.
     297   * I can ask Victor to tell me the node state.
     298 I'll pursue whichever of those comes back more quickly, and that will be it for this test.
     299
    252300=== Step 3D: GPO requests access to IPMI management interfaces for workers ===
    253301