Index: /trunk/doc/design/hardware_mgt.tex
===================================================================
--- /trunk/doc/design/hardware_mgt.tex	(revision 2243)
+++ /trunk/doc/design/hardware_mgt.tex	(revision 2244)
@@ -44,9 +44,12 @@
 \section{Introduction}
 
+\subsection{Scope}
+
 This document presents the strategy for managing the PS1 IPP Cluster through
-it's life-cycle which will span a period of approximately 3 years.  The plan
-covers hardware setup, validation, and operations.  The life-cycle has been
-broken down into three primary phases which in some cases have been decomposed
-into smaller stages and steps for clarity.
+it's projected life-cycle which will span a period of approximately 3 years.
+The plan covers hardware setup, validation, operations, and graceful
+decommissioning.  The life-cycle has been broken down into three primary phases
+which in some cases have been decomposed into smaller stages and steps for
+clarity.
 
 \section{Life-Cycle}
@@ -61,9 +64,8 @@
 \subsubsection{Stage 1}
 
-
 This covers the installation of the nodes, the network equipment plus specing
 and acquiring the cluster cabling and the management equipment.  Followed by
-the testing of the complete system.   This stage should cover approximately 75
-working days.
+the testing of the integrated system.   This stage should cover approximately
+75 working days.
 
 \paragraph{Step 1}
@@ -72,16 +74,61 @@
 additional racks for the core switch and management equipment.  The racks will
 need to be unpackaged, inspected for physical damage, and positioned in the
-data center.  Once the racks are in their final configuration and the core
-switch has been mounted, the lengths for network and management cabling will
-be measured and the appropriate cabling ordered.  In addition, the type
-(110v/220v) and number of network managed power strips that are required will
-have to be determined and ordered.  There will be a slack period of
-approximately one month awaiting order fulfillment.
+data center.
+
+Once the racks are in their final configuration and the core switch has been
+mounted, the lengths for network and console server cabling will be measured
+and the appropriate cabling ordered.  The network cabling shall be black PVC or
+Plenum rated Category 6 RJ-45 patch cables.  The network console server cabling
+shall be red PVC or Plenum rated Category 6 RJ-45 patch cables.
+
+Console server server equipment and network managed power strips will then be
+ordered.  The number and type of network managed power strips will depend on
+whether 110v or 220v electricity is available.  The console server equipment and
+managed power strips should inter-operate to provide a unified cluster
+management system.
+
+There will be a slack period of approximately one month awaiting order
+fulfillment.
 
 \paragraph{Step 2}
 
-The network and console wiring will be installed and connected to the ether
-the core switch or the console servers.  The IPP Cluster Test Plan can then
-begin.
+The network and console wiring will be installed and connected to the ether the
+core switch or the console servers.  The node naming convention shall be in the
+format of "ippxxx", where "xxx" is an integer sequentially assigned from the
+range [000..999].  Each node shall have one of it's gigabit Ethernet ports
+connected to the core switch by a Category 6 network patch cable.  The core
+switch shall have four 48-port gigabit Ethernet modules and one fourth of the
+nodes shall be connected to each of those modules.  The core switch shall be
+configured such that all of the Ethernet ports are in the same VLAN.
+
+The nodes shall have a \tbd{Linux 2.6 based operating system that meets the
+requirements defined in Software Requirements Specification (PSDC-430-005)}
+installed on them.  This shall be accomplished by setting up temporary DHCP and
+TFTP servers, booting the nodes from the network via PXE, and installing a
+local operating system image with SystemImager.  The nodes shall each be
+assigned a permanent IP address in an RFC 1519 Class C equivalent or larger
+address space.  If private IP address space, as defined in RFC 1918, is to be
+used for the IPP Cluster then special coordination will need to be made with
+the IFA due to possible network routing issues between other PS1 data systems
+and the IPP Cluster.  The IP address allocation for the nodes shall be
+sequentially from the beginning of the address space with the first two IP
+address reserved for the gateway.  \tbd{The IP address of all of the IPP
+cluster nodes should be recorded into the "/etc/hosts" file on every node to
+prevent DNS look-ups during inter-cluster communication} 
+
+\begin{center}
+\begin{tabular}{ll}
+Node    &IP address\\
+\cline{1-2}
+(reserved)  &x.x.x.1\\
+(reserved)  &x.x.x.2\\
+ipp000      &x.x.x.3\\
+ipp001      &x.x.x.4\\
+ipp002      &x.x.x.5\\
+\cline{1-2}
+\end{tabular}
+\end{center}
+
+The IPP Cluster Test Plan can then begin.
 
 \subsubsection{Stage 2}
@@ -129,4 +176,6 @@
 deactivated.  The deactivated nodes shall be stored for possible reuse with
 PS4.  This phase will last approximate one year.
+
+\pagebreak
 
 \section{Schedule}