Commit 0c2ba789 authored by Mike Hibler's avatar Mike Hibler
Browse files

updates

parent 7910614b
......@@ -30,6 +30,12 @@ B. If the node is of a new type
net (ie 4), how long you should make people wait before power cycling
again, the default image id, delay capacity, control iface (ie
eth4), and the OS id to boot when it is acting as a delay node.
Example:
insert into node_types
(class,type,proc,speed,RAM,HD,max_cards,max_ports,osid,control_net,imageid,imageable,delay_capacity,control_iface,delay_osid,pxe_boot_path)
values
("pc","pc2000","P4",2000,512,20.0,5,1,"RHL-STD",0,"UTAHPC-FBSD45+LINUX71",1,2,"eth0","FBSD-STD","boss.emulab.net:/tftpboot/pxeboot");
2. There are several scripts that limit searches to certain
types. You'll need to include this new type as appropriate.
......@@ -108,7 +114,7 @@ C. What to do on boss:
6. Add the node to the system files:
- DNS: on boss, cd /etc/namedb
co -l emulab.db.head
co -l emulab.net.db.head
add these lines with all the others:
pcN IN A 155.101.132.N
IN MX 10 ops
......@@ -122,17 +128,17 @@ C. What to do on boss:
N IN PTR pcN.emulab.net.
ci -u 155.101.132.db
run /usr/testbed/sbin/named_setup to update.
- DHCP: on boss, cd /usr/local/etc/ (old /usr/site/bin/dhcp/)
edit dhcpd.conf
add these lines:
# pcN
host 155.101.132.N {
hardware ethernet 00:01:23:45:67:AF; # control
option host-name "pcN";
fixed-address 155.101.132.N;
}
sudo /usr/local/etc/rc.d/dhcpd.sh restart
(old /usr/site/bin/dhcp/restart)
- DHCP: on boss, cd /usr/local/etc/
if you added a new node type, then you need to add a line
of the form:
%%nodetype=<type>
(where <type> is the new type is called) to dhcpd.conf.template.
Then as root run:
dhcpd_makeconf dhcpd.conf.template > Ndhcpd.conf
you can diff dhcpd.conf with the new file to verify nothing
catostrophic happened. Finally:
sudo cp Ndhcpd.conf dhcpd.conf
sudo /usr/local/etc/rc.d/2.dhcpd.sh restart
- tip: on ops, edit /etc/remote
add a line like this:
pcN:dv=/dev/tip/pcN:br#115200:nt:pa=none:
......
......@@ -34,7 +34,10 @@ A. FreeBSD (while running single user):
Generate new host keys. Actually, copy from an existing image.
* /etc/testbed/{client,emulab}.pem
Generate a new one.
Generate a new one. From Leigh:
Just need to cd into the ssl directory and do a gmake
(on their boss of course!) then a gmake boss-installX.
The images need emulab.pem and client.pem from that directory.
* /etc/testbed/supfile
Fix release tag (FBSD*) if necessary and host=
......@@ -82,7 +85,10 @@ B. While running Linux (single user):
Change the root password, this file will get installed by prepare.
* /etc/testbed/{client,emulab}.pem
Generate a new one.
Generate a new one. From Leigh:
Just need to cd into the ssl directory and do a gmake
(on their boss of course!) then a gmake boss-installX.
The images need emulab.pem and client.pem from that directory.
* /etc/testbed/supfile
Fix release tag (RHL*) if necessary and host=
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment