Changeset 2249 for trunk/doc/design/hardware_mgt.tex

Timestamp:

Nov 1, 2004, 11:22:29 AM (22 years ago)

Author:

jhoblitt

Message:

expanded details
partial list of tests

File:

• trunk/doc/design/hardware_mgt.tex (modified) (9 diffs)

trunk/doc/design/hardware_mgt.tex

@@ -98 +98 @@
 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
+switch has 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.
 
@@ -110 +110 @@
 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} 
-
+the Pan-STARRS Global Systems group 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{figure}
 \begin{center}
 \begin{tabular}{ll}
@@ -128 +129 @@
 \cline{1-2}
 \end{tabular}
+\caption{ \label{addressing} IP Addressing}
 \end{center}
+\end{figure}
 
 The IPP Cluster Test Plan can then begin.
@@ -135 +138 @@
 
 The cluster enters into a period of partial dormancy where all but 6 of the
-nodes are deactivated.  The remaining 6 nodes are to remain available for the
-testing of IPP software.  The duration of this stage will vary as Stage 3 won't
-begging until PS1 is almost ready to start taking data.  The minimum duration
-is 2.5 months.
+nodes are deactivated.  The remaining active nodes are to each have 12 disks
+from the pool of commisioning disks installed and configured as a single RAID 5
+volume.  These nodes are to remain available for the testing of IPP software
+until the cluster enters into it's production phase.  The duration of this
+stage will vary as Stage 3 won't begging until PS1 is almost ready to start
+taking data.  The minimum duration of this stage is 2.5 months.
 
 \subsubsection{Stage 3}
 
-The 1st lot of storage disks are ordered and the complete cluster is brought
+The $1^{st}$ lot of storage disks are ordered and the complete cluster is brought
 on line and prepared for production.
 
 \paragraph{Step 1}
 
-Approximately 4 months before the IPP Cluster needs to be fully operational
-the first lot of disks (600) shall be ordered.  There will be a slack period
-of approximately 2-3 months while the purchase is approved and delivery is
-completed.
+Approximately 4 months before the IPP Cluster needs to be fully operational the
+first lot of disks (600) shall be ordered.  The disks ordered should be the of
+the largest commonly avaiable capacity.  It is estimated that this will be
+400GB per disk when this stage is reached.  The disks maybe purchase lose or
+pre-installed in drive sleds if possible.  The disks most have a 3 year
+warrenty either from the OEM or the disk manufacturer.  There will be a slack
+period of approximately 2-3 months while the purchase is approved and delivery
+is completed.
 
 \paragraph{Step 2}
 
-All IPP nodes are activated and subsections x-y of the IPP Cluster Test Plan are
-re-run.  Concurrently the new disks will be mounted into drive sleds, the
-disk mounting should take approximately 50 hours of labor.  The 1st lot of
-disks shall then be run through the IPP Storage Test Plan.
+All IPP nodes are activated and subsections x-y of the IPP Cluster Test Plan
+are re-run.  If the $1^{st}$ lot of disks are purcashed lose they will be
+concurrently mounted into drive sleds, the disk mounting should take
+approximately 50 hours of labor.  The new disks shall then be run through the
+IPP Storage Test Plan.
 
 \subsection{Production}
@@ -169 +179 @@
 The production phase will last approximately two years.
 
+\subsubsection{disks ordered}
+
+The $2^{nd}$ lot of storage disks are ordered, installed and tested.
+
+\subsubsection{disks ordered}
+
+The $3^{rd}$ lot of storage disks are ordered, installed and tested.
+
 \subsection{End of Life}
 
@@ -177 +195 @@
 PS4.  This phase will last approximate one year.
 
-\pagebreak
-
 \section{Schedule}
 
+\begin{figure}
 \begin{center}
 \begin{tabular}{ll}
-Manpower Estimate&\\
 \cline{1-2}
 Commissioning           &\\
@@ -197 +213 @@
 \cline{1-2}
 \end{tabular}
+\caption{ \label{manpower} Estimated Manpower}
 \end{center}
+\end{figure}
 
 \begin{figure}
@@ -210 +228 @@
 \appendix
 
+\pagebreak
 \section{IPP Cluster Test Plan}
 
@@ -245 +264 @@
 \subsubsection{Planned tests}
 
-\paragraph{Node hardware}
+\paragraph{Node}
+
+physical inventory
+all 3 power supplies power up
+memory passes memtest86+
+O/S boots
+sees both CPUs at the proper clock rate
+sees the full ammount of memory
+sees all the PCI devices
+sees the root disk
+both gige interfaces can be configured and a test device pinged
+RAID controllers report their status as OK
 
 \paragraph{Network hardware}
 
+physical inventory
+sh version reports the proper ammount of memory
+sh module shows all the modules with status OK
+sh diagnostics power-on
+
 \paragraph{Management hardware}
 
+\pagebreak
 \section{IPP Storage Test Plan}