| 889 | I'm not sure why this test only mentions the experiment nodes, and not the control node; I'd think that we'd especially want ILO access to that. |
| 890 | |
| 891 | The control node's ILO IP address is in DNS: |
| 892 | |
| 893 | {{{ |
| 894 | [23:22:39] jbs@boss.instageni.gpolab.bbn.com:/users/jbs |
| 895 | +$ host -l 129/25.242.1.192.in-addr.arpa | grep ilo |
| 896 | 131.129/25.242.1.192.in-addr.arpa domain name pointer control-ilo.instageni.gpolab.bbn.com. |
| 897 | }}} |
| 898 | |
| 899 | I was able to SSH to elabman@control-ilo.instageni.gpolab.bbn.com, using the password in boss:/usr/testbed/etc/ilo.pswd. |
| 900 | |
| 901 | Once there, I used 'help power' to show some power-control type commands. I created InstaGENI ticket [instaticket:72] to track the task of documenting this somewhere, although 'help' and then 'help power' is pretty intuitive. I didn't actually try any power commands on the control node. |
| 902 | |
| 903 | I then used the 'textcons' command to get a text console, where I saw a bunch of syslog messages, hit return a few times, and found myself at a "gpolab.control-nodes.geniracks.net login:" prompt. I wasn't able to log in as 'jbs' with my ProtoGENI password, which makes sense; how would my password have gotten set? And in fact I don't have one: |
| 904 | |
| 905 | {{{ |
| 906 | [23:31:44] jbs@gpolab:/home/jbs |
| 907 | +$ sudo grep jbs /etc/shadow |
| 908 | jbs:*:15682:0:99999:7::: |
| 909 | }}} |
| 910 | |
| 911 | I set myself one, with 'sudo passwd jbs', but still wasn't able to log in. Also, the login prompt seemed to change from "gpolab.control-nodes.geniracks.net login:" to "gpolab login:", and back again, at seemingly random times. I mentioned this on IG ticket [instaticket:72] too. |
| 912 | |
| 913 | I was able to SSH to elabman@192.1.242.182, the ILO for pc3, and observe the console in boot wait mode. I reset the system with 'power reset', and that seemed to work. I noted on IG ticket [instaticket:72] that the ILO addresses for the experiment nodes aren't in DNS. |
| 914 | |
| 915 | === Results of testing step 3G: 2012-05-16 === |
| 916 | |
| 1056 | |
| 1057 | === Results of testing step 3H: 2012-12-20 === |
| 1058 | |
| 1059 | I allocated an exclusive experiment node, with this rspec: |
| 1060 | |
| 1061 | {{{ |
| 1062 | <?xml version="1.0" encoding="UTF-8"?> |
| 1063 | <!-- |
| 1064 | This rspec will reserve one PG host in the InstaGENI rack at BBN, running |
| 1065 | Ubuntu 10.04. |
| 1066 | |
| 1067 | AM: https://instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am |
| 1068 | --> |
| 1069 | |
| 1070 | <rspec xmlns="http://www.geni.net/resources/rspec/3" |
| 1071 | xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" |
| 1072 | xs:schemaLocation="http://www.geni.net/resources/rspec/3 |
| 1073 | http://www.geni.net/resources/rspec/3/request.xsd" |
| 1074 | type="request"> |
| 1075 | |
| 1076 | <node client_id="carlin" exclusive="true"> |
| 1077 | <sliver_type name="raw"> |
| 1078 | <disk_image name="urn:publicid:IDN+instageni.gpolab.bbn.com+image+emulab-ops:UBUNTU12-64-STD" /> |
| 1079 | </sliver_type> |
| 1080 | </node> |
| 1081 | |
| 1082 | </rspec> |
| 1083 | }}} |
| 1084 | |
| 1085 | My manifest rspec said that I got pc3.instageni.gpolab.bbn.com. |
| 1086 | |
| 1087 | After it became ready, I confirmed that I could log in to it as myself as usual, i.e. that sshd was up and running properly. |
| 1088 | |
| 1089 | I then confirmed that I could log in from boss to pc3, and run commands as root: |
| 1090 | |
| 1091 | {{{ |
| 1092 | [00:13:04] jbs@boss.instageni.gpolab.bbn.com:/users/jbs |
| 1093 | +$ sudo ssh pc3 whoami |
| 1094 | root |
| 1095 | |
| 1096 | [00:13:11] jbs@boss.instageni.gpolab.bbn.com:/users/jbs |
| 1097 | +$ sudo ssh pc3 uname -a |
| 1098 | Linux carlin.jbs.pgeni-gpolab-bbn-com.instageni.gpolab.bbn.com 2.6.38.7-1.0emulab #1 SMP Wed Aug 24 09:55:34 MDT 2011 x86_64 x86_64 x86_64 GNU/Linux |
| 1099 | }}} |