Changes between Version 10 and Version 11 of GENIRacksHome/InstageniRacks/ConfirmationTestStatus/Kettering


Ignore:
Timestamp:
05/21/13 14:17:50 (6 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/InstageniRacks/ConfirmationTestStatus/Kettering

    v10 v11  
    10901090== IG-CT-6 - Administrative Tests ==
    10911091
     1092Sent request for administrative account to site contact from the [http://groups.geni.net/geni/wiki/GeniAggregate/KetteringInstaGENI Kettering InstaGENI] aggregate page.  Followed instructions at [https://users.emulab.net/trac/protogeni/wiki/RackAdminAccounts Admin Accounts on InstaGeni Racks] page for account request. A local admin account was create and also had to join the ''emulab-ops'' group at https://www.kettering.edu/joinproject.php3?target_pid=emulab-ops.   Once account was create and membership to emulab-ops was approved proceeded to execute administrative tests. 
     1093
     1094
     1095{{{
     1096LNM:~$ ssh lnevers@control.kettering.edu
     1097
     1098}}}
     1099
     1100Also access the node via the PG Boss alias:
     1101{{{
     1102LNM:~$ ssh boss.kettering.edu
     1103}}}
     1104
     1105Further verified access by ssh from ops.instageni.gpolab.bbn.com to boss.instageni.gpolab.bbn.com, which is usually restricted for non-admin users:
     1106{{{
     1107LNM:~$ ssh ops.kettering.edu
     1108
     1109}}}
     1110From boss node accessed each of the experiment nodes that support VMs:
     1111{{{
     1112[lnevers@boss ~]$ for i in pc1 pc2; do ssh $i "echo -n '===> Host: ';hostname;sudo whoami;uname -a;echo"; done
     1113
     1114}}}
     1115
     1116In order to access Dedicated Nodes some experiment must be running on the raw-pc device. At the time of this capture two raw-pc nodes were in use (pcX and pcY):
     1117{{{
     1118[lnevers@boss ~]$ sudo ssh pcX
     1119[root@pcX ~]# sudo whoami
     1120root
     1121[root@pcX ~]# exit
     1122logout
     1123Connection to pcX.kettering.edu
     1124[lnevers@boss ~]$ sudo ssh pcY
     1125[root@pc ~]# sudo whoami
     1126root
     1127[root@pc ~]#
     1128}}}
     1129
     1130Access infrastructure Switches using documented password. First connect to the switch named procurve1 the control network switch:
     1131{{{
     1132[lnevers@boss ~]$ sudo more /usr/testbed/etc/switch.pswd
     1133XXXXXXXXX
     1134[lnevers@boss ~]$ telnet procurve1
     1135
     1136
     1137}}}
     1138
     1139Connect to the switch named procurve2 the dataplane network switch via ssh using the documented password:
     1140{{{
     1141[lnevers@boss ~]$ sudo more /usr/testbed/etc/switch.pswd
     1142xxxxxxx
     1143[lnevers@boss ~]$ ssh manager@procurve2
     1144}}}
     1145
     1146Access the FOAM VM and gather information for version
     1147{{{
     1148LNM:~$ ssh lnevers@foam.kettering.edu
     1149
     1150sudo foamctl admin:get-version  --passwd-file=/etc/foam.passwd
     1151
     1152}}}
     1153Check FOAM configuration for  site.admin.email, geni.site-tag, email.from settings:
     1154{{{
     1155foamctl config:get-value --key="site.admin.email"  --passwd-file=/etc/foam.passwd
     1156
     1157foamctl config:get-value --key="geni.site-tag"  --passwd-file=/etc/foam.passwd
     1158
     1159foamctl config:get-value --key="email.from"  --passwd-file=/etc/foam.passwd
     1160
     1161# check if FOAM auto-approve is on. Value 2 = auto-approve is on.
     1162
     1163foamctl config:get-value --key="geni.approval.approve-on-creation"  --passwd-file=/etc/foam.passwd
     1164
     1165}}}
     1166
     1167Show FOAM slivers and details for one sliver:
     1168
     1169{{{
     1170foamctl geni:list-slivers --passwd-file=/etc/foam.passwd
     1171
     1172}}}
     1173Access the FlowVisor VM and gather version information:
     1174{{{
     1175
     1176ssh lnevers@flowvisor.kettering.edu
     1177}}}
     1178Check the !FlowVisor version, list of devices, get details for a device, list of active slices, and details for one of the slices:
     1179{{{     
     1180
     1181fvctl --passwd-file=/etc/flowvisor.passwd ping hello
     1182
     1183# Devices
     1184fvctl --passwd-file=/etc/flowvisor.passwd listDevices
     1185
     1186fvctl --passwd-file=/etc/flowvisor.passwd getDeviceInfo 06:d6:6c:3b:e5:68:00:00
     1187
     1188#Slices
     1189fvctl --passwd-file=/etc/flowvisor.passwd listSlices
     1190
     1191fvctl --passwd-file=/etc/flowvisor.passwd getSliceInfo 5c956f94-5e05-40b5-948f-34d0149d9182
     1192
     1193}}}
     1194
     1195Check the FlowVisor setting:
     1196{{{
     1197fvctl --passwd-file=/etc/flowvisor.passwd dumpConfig /tmp/flowvisor-config
     1198more /tmp/flowvisor-config
     1199
     1200}}}
     1201
     1202
     1203Verify alerts for the compute resource Aggregate Manager are being reported to the [http://monitor.gpolab.bbn.com/nagios/cgi-bin/status.cgi GPO Tango GENI Nagios monitoring] and that all alerts have status OK.
     1204
     1205
     1206[[Image(Kettering-nagios.jpg)]]
     1207
     1208Verify alerts for the FOAM Aggregate Manager are being reported to the [http://monitor.gpolab.bbn.com/nagios/cgi-bin/status.cgi GPO Tango GENI Nagios monitoring] and that all alerts have status OK.
     1209
     1210[[Image(Kettering-OF-nagios.jpg)]]
     1211
    10921212----
    10931213{{{