Changes between Version 42 and Version 43 of Installation/Nodes

Timestamp:

Sep 25, 2013 8:18:40 PM (11 years ago)

Author:

jhickey

Comment:

--

Installation/Nodes

@@ -133 +133 @@
 }}}
 
-=== Setting up MFS images to use the serial console ===
-
-By default, the MFS images are set to use the video card as the console device.  Before you start, please familiarize yourself with [http://www.freebsd.org/doc/en/books/handbook/serialconsole-setup.html the basics of FreeBSD serial consoles].
-
-==== Figure out which serial port you will be using ====
-
-A serial console is typically used in conjunction with IPMI.  Sometimes IPMI gives access to the COM1 serial interface of a machine (for example HP DL160G6 servers use COM1).  Other systems dedicate the COM2 port to the IPMI embedded server.  You will have to figure out how your particular hardware is setup.  Some of these steps will be handled by the setup_mfs script in the future.
-
-==== Set the proper baud rate in your systems BIOS ====
-
-By default, we use 115200 as the baud rate for all MFS images.  This is a compile time value, so it is best to use 115200.
-
-==== Installing a PXE boot loader ====
-
-When the PXE boot ROM is loaded during machine boot. 
-
-The default bootloader for testbed nodes is /tftpboot/pxeboot.emu.  There are four different versions of pxeboot.emu distributed with the tarball.
-
- * pxeboot-null.emu : Does not display pxeloader prompt
- * pxeboot-com1.emu  : Displays pxeloader prompt via COM1 serial port
- * pxeboot-com2.emu : Displays pxeloader prompt via COM2 serial port
- * pxeboot.emu  : Displays pxeloader prompt via video out
-
-Pick a loader that best suits your installation and copy it (backing up the VGA boot loader first):
-
-{{{
- cp /tftpboot/pxeboot.emu /tftpboot/pxeboot-vga.emu
- cp /tftpboot/pxeboot.emu-<null|sio|sio2|vga> /tftpboot/pxeboot.emu
-}}}
-
-You can also look at modifying '''/usr/local/etc/dhcpd.conf.template''' to use different boot loaders for different machines.  You will have to generate a new dhcpd.conf configuration using '''/usr/testbed/sbin/dhcpd_makeconf -i -r'''.
-
-
-==== Setting up a MFS image to use the serial console =====
-
-Edit the file loader.conf.orig for each MFS image:
-
-{{{
-[jjh@boss /tftpboot]$ find /tftpboot/ -name loader.conf.orig
-/tftpboot/freebsd/boot/loader.conf.orig
-/tftpboot/freebsd.newnode/boot/loader.conf.orig
-/tftpboot/frisbee/boot/loader.conf.orig
-}}}
-
-At the top of the loader.conf.orig file you will be presented with three choices:
-
-{{{
-##
-## Pick a console:
-##
-## "comconsole"  If you are using a serial port as your console
-## "vidconsole"  If you are using the VGA as your console on your nodes
-## "nullconsole" If you don't have VGA or serial lines, and it appears that
-##               nodes are not booting, try using this, which gives you a
-##               non-interactive version of the boot loader.  Some sites
-##               have had problems with "phantom" serial line input from a
-##               non-existant serial line causing the comconsole version of
-##               the boot loader to drop into interactive mode.
-##
-console="comconsole"
-#console="vidconsole"
-#console="nullconsole"
-}}}
-
-==== Setting up  a MFS image to use the second COM port ====
-
-FreeBSD picks the serial console based on a special flag for the UART you want to use.  UART 0 is COM1 and UART 1 is COM2.  
-
-{{{
-[jjh@boss /tftpboot]$ find . -name device.hints -exec grep flags {} \; | grep uart
-hint.uart.0.flags="0x10"
-hint.uart.0.flags="0x10"
-hint.uart.0.flags="0x10"
-}}}
-
-To use COM2, the second UART, change the '''hint.uart.0.flags''' to '''hint.uart.1.flags'''
-
-==== Making the configuration changes for each image stick ====
-
-You will have to run the '''prepare''' script in each boot directory after changing loader.conf.orig or the device.hints file.
-
-{{{
-root@boss:/tftpboot/freebsd/boot # ./prepare
-loader.conf: loader.conf.gz updated...
-loader.rc: 
-kernel: 
-mfsroot: 
-}}}
-
 = Testbed Nodes =
 
@@ -232 +143 @@
 The testbed nodes should be set to boot only off of the network.  Disable hard drive boot to prevent failed PXE requests from falling through to booting whatever is on the disk.
 
-
-
 == Node Types ==
+
+=== Select a console type === 
+
+This setting will determine which MFS the node will boot.  If you are using a serial port, please be aware that by default, we use 115200 as the baud rate for all MFS images.  This is a compile time value, so it is best to use 115200. 
 
 === Determining the disk type ===
@@ -299 +212 @@
 If you are creating a node type for a typical testbed pc, use the class 'pc.'  If you are creating a node type for special hardware, choose something else such as 'router' for routers or 'appliance' for appliance type nodes.
 
+
+=== Associating Operating System images with your new node type ===
+
+After creating a new node type, you will need to enable support for it with each operating system image.  This can be accomplished by editing the operating system image through the web interface and selecting the new type.  On new installs, you can also cheat with the SQL command below.  Be sure to substitute '''minipc''' with the node type you created.
+
+{{{
+mysql> insert into osidtoimageid select default_osid as osid, 'minipc' as type, imageid from images;
+Query OK, 5 rows affected (0.00 sec)
+Records: 5  Duplicates: 0  Warnings: 0
+
+mysql> select * from osidtoimageid;
++-------+--------+---------+
+| osid  | type   | imageid |
++-------+--------+---------+
+| 10007 | minipc |   10007 |
+| 10009 | minipc |   10009 |
+| 10005 | minipc |   10005 |
+| 10008 | minipc |   10008 |
+| 10006 | minipc |   10006 |
++-------+--------+---------+
+5 rows in set (0.00 sec)
+}}}
+
 == Manually adding non-standard nodes ==
 === Create the node type ===