Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
emulab-devel
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
143
Issues
143
List
Boards
Labels
Service Desk
Milestones
Merge Requests
6
Merge Requests
6
Operations
Operations
Incidents
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
emulab
emulab-devel
Commits
e8858f3e
Commit
e8858f3e
authored
Dec 12, 2012
by
Leigh B Stoller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Updates after BBN install.
parent
f06f1d99
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
69 additions
and
15 deletions
+69
-15
install/genirack/Images.txt
install/genirack/Images.txt
+8
-5
install/genirack/NOTES
install/genirack/NOTES
+61
-10
No files found.
install/genirack/Images.txt
View file @
e8858f3e
...
...
@@ -65,15 +65,18 @@ inner ops!
Now we convert the VMs for boot in the target environment, which means
cleaning up some stuff and changing a bunch of things. First ssh (as
root) into the inner
op
s VM from outer boss:
root) into the inner
bos
s VM from outer boss:
op
s> cd /usr/testbed/obj/testbed/install
ops> sudo perl emulab-install -i ops/genirack op
s
bos
s> cd /usr/testbed/obj/testbed/install
boss> sudo perl emulab-install -c -i boss/genirack bos
s
then log out and ssh (as root) into inner
bos
s:
then log out and ssh (as root) into inner
op
s:
ops> cd /usr/testbed/obj/testbed/install
ops> sudo perl emulab-install -i boss/genirack boss
ops> sudo perl emulab-install -i ops/genirack ops
Grab /usr/testbed/etc/elabman.pswd and store it in our file. See
Utah boss:~stoller/genirack/pswd.txt.
Now we have to shutdown the VMs. Log into the physical host and then:
...
...
install/genirack/NOTES
View file @
e8858f3e
...
...
@@ -150,11 +150,13 @@ Setting up an InstaGeni Rack. First, we need the following info:
2610(vlan-10)> untagged 23 XXXX Make sure about port number!
2610(vlan-10)> ip address 10.1.1.253/24
2610(vlan-10)> exit
2610(config)> no vlan 1 ip address
2610(config)> vlan 1
2610(vlan-1)> ip address 10.254.254.253/24 # IGMP querier requires this
2610(vlan-1)> exit
2610(config)> management-vlan 10
2610(config)> ip default-gateway 10.1.1.254
2610(config)> vlan 1 ip igmp
2610(config)> vlan 1
1
ip igmp querier
2610(config)> vlan 1 ip igmp querier
2610(config)> no web-management
2610(config)> no snmp-server community public
2610(config)> snmp-server community XXXXX manager unrestricted
...
...
@@ -247,19 +249,68 @@ Setting up an InstaGeni Rack. First, we need the following info:
* Restore the VMs:
~elabman/clientside/tmcc/linux/xen/restorevm.pl -i boss /scratch/boss
~elabman/clientside/tmcc/linux/xen/restorevm.pl -i ops /scratch/ops
mkdir ~elabman/boss ~elabman/ops
~elabman/restorevm.pl -t ~elabman/boss -i boss /scratch/boss
~elabman/restorevm.pl -t ~elabman/ops -i ops /scratch/ops
This creates a bunch of LVMs and rewrites the xm.conf in the
boss/ops directories to reflect the new LVM paths, etc.
* Fire up the VMs. Ops has to be first, followed by boss.
sudo xm create
/scratch
/ops/xm.conf
sudo xm create
~elabman
/ops/xm.conf
sleep 30
sudo xm create
/scratch
/boss/xm.conf
sudo xm create
~elabman
/boss/xm.conf
* The rest of the setup has not been written down yet. We are waiting
for a second rack, to nail down the rest of the instructions.
* Anything to do with FOAM is in Nick's capable hands!
* It is possible that ops will hang on fixarp, because tmcd is not
running on boss yet. Log into boss and do:
sudo testbed-control boot
which should get ops running.
* Now it is time to power on the experimental nodes. If all goes well,
they will boot up into FreeBSD MFS and be in the hwdown experiment.
Before we release them, we want to change some settings on the ilo.
The following command will change the Admin password, create an
elabman user, load its ssh key, change the boot order, etc, etc.
This part is not scripted yet, so need to look at this XML file.
/usr/testbed/etc/genirack/ilo.xml.
In this file, the mapping of pcX to slot is:
pc1 -> U05
pc2 -> U06
pc3 -> U07
pc4 -> U08
pc5 -> U09
So grab the ilo password for each one, and then:
perl /usr/testbed/obj/testbed/install/genirack/initilo.pl <ilopswd> pc1
perl /usr/testbed/obj/testbed/install/genirack/initilo.pl <ilopswd> pc2
perl /usr/testbed/obj/testbed/install/genirack/initilo.pl <ilopswd> pc3
perl /usr/testbed/obj/testbed/install/genirack/initilo.pl <ilopswd> pc4
perl /usr/testbed/obj/testbed/install/genirack/initilo.pl <ilopswd> pc5
perl /usr/testbed/obj/testbed/install/genirack/initilo.pl <ip> <ilopswd>
The last line updates the control node ilo.
* Free all the nodes up and lets hope they reload okay. Okay, lets
just do one to start with.
wap nfree emulab-ops hwdown pc1
If that works and pc1 does indeed go into the free pool, then do the
rest of the nodes:
wap nfree emulab-ops hwdown pc2 pc3 pc4 pc5
* Create some test experiments.
---
Problems:
root/toor password on boss did not match what is in the file.
root/toor password on ops is generated elabinelab swapin and needs to set.
ntpd and ntpdate failures.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment