Differences between version 41 and revision by previous author of WlugBladeServer.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 41 | Last edited on Saturday, November 14, 2009 7:09:33 am | by BruceKingsbury | Revert |
| Older page: | version 37 | Last edited on Saturday, October 17, 2009 11:44:44 pm | by AristotlePagaltzis | Revert |
@@ -35,13 +35,13 @@
| 2 | <tt>mail</tt> |60.234.66.115|Done|Set|10.100.100.4 |Syncs to db|OK| |
| 3 | <tt>www1</tt> |60.234.66.116|Done|Set|10.100.100.2 |Syncs to db|OK| |
| 4 | <tt>www2</tt> |60.234.66.117|Done|Set|10.100.100.3 |Syncs to db|OK| | disk errors
| 5 | <tt>db</tt> |60.234.66.118|Done|Set|10.100.100.1 |Syncs to nz.pool.ntp.org|OK| |
-| 6 | | | | | | | | | runs ubuntu
, not configured
-| 7 | | | | | | | | | runs ubuntu, not configured
-| 8 | (will become hoiho)
| | | | | | | | runs debian 5
, new hdd, no public
network connectivity yet
+| 6 | (will become hoiho)
| | | | | | | | runs debian 5
, new 120GB hdd
+| 7 | | | | | | | | | runs ubuntu, not configured, some disk errors
+| 8 | | | | | | | | | empty bay
, possibly faulty
network socket?
+| 9 | | | | | | | | | Spare blade, runs ubuntu
?>
-
<tt>hoiho</tt>::
* relaxed FireWall~ing?
<tt>mail</tt>::
@@ -68,9 +68,13 @@
* [Debian GNU/Linux Installation Guide: Preparing Files for TFTP Net Booting | http://www.debian.org/releases/stable/i386/ch04s05.html.en]
* [Setting Up A PXE Install Server For Multiple Linux Distributions On Debian Lenny | http://www.howtoforge.com/setting-up-a-pxe-install-server-for-multiple-linux-distributions-on-debian-lenny] (basically the same stuff, condensed)
-Only
the bottom row (<tt>eth0<
/tt>
) can be [PXE]-booted. Hopefully
the <tt>hoiho</tt> chassis has
been configured with this as the "private" network
. It's possibly also a good idea to lock down [PXE] boot to specific [MAC] addresses so no other blades can accidentally be [PXE] booted into the installer.
+On
the same blade running dhcpd
/tftpd I also configured NAT (and squid
) so that the debian installer
can fetch packages without
the blade being exposed to the public internet at all until after it's
been fully
configured and firewalled
.
+
+
It's possibly also a good idea to lock down [PXE] boot to specific [MAC] addresses so no other blades can accidentally be [PXE] booted into the installer.
+
+Only the bottom row network interfaces(<tt>eth0</tt>) can be [PXE]-booted. It seems the <tt>hoiho</tt> chassis has been configured with this as the "public" network so perhaps we should consider changing these around?
!! Files to edit
<tt>/var/lib/tftpboot/debian-installer/i386/boot-screens/menu.cfg</tt>::
@@ -100,4 +104,14 @@
* proper network config
* FireWall rules
* more secure [SSH] settings
* [LDAP]?
+
+<?plugin OldStyleTable
+| __#__ | __Name__ | __RW IP__ (eth1) | __FireWall__ | __Root password__ | __Private IP__ (eth0)| __[NTP]__ | __Serial Console__ | __Compaq Tools__ | __Notes__
+| 1 | <tt>korora</tt> |10.1.1.20| no |Set|10.100.100.20 | |OK | | 1G ram, pxe server, squid proxy
+| 2 | <tt>blade</tt> |none| no |Set|DHCP | |OK | | 1G ram
+| 3 | <tt>blade</tt> |none| no |Set|DHCP | |OK | |
+| 4 | <tt>blade</tt> |none| no |Set|DHCP | |OK | |
+| 5 | <tt>blade</tt> |none| no |Set|DHCP | |OK | |
+| 6 | <tt>blade</tt> |none| no |Set|DHCP | |OK | |
+?>
