IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changeset 2395


Ignore:
Timestamp:
Nov 22, 2004, 4:05:31 PM (22 years ago)
Author:
jhoblitt
Message:

minor edits
added maintenance section

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/design/hardware_mgt.tex

    r2394 r2395  
    6464phase is broken down into three discrete stages.
    6565
    66 \subsubsection{Stage 1}
     66\subsubsection{Setup}
    6767
    6868This covers the installation of the nodes, the network equipment plus specing
     
    7474
    7575The IPP nodes will arrive pre-installed into standard 42U racks along with 1-2
    76 additional racks for the core switch and management equipment.  The shipment
    77 will need to be unpackaged, inventoried, inspected for physical damage, and
    78 positioned in the data center.
     76additional racks for the core switch and management equipment.  There will also
     77be a small pool of hard disks included with the shipment for the testing of the
     78RAID controllers.  The shipment will need to be unpackaged, inventoried,
     79inspected for physical damage, and positioned in the data center.
    7980
    8081Once the racks are in their final configuration and the core switch has been
     
    8485shall be red PVC or Plenum rated Category 6 RJ-45 patch cables.
    8586
    86 Console server equipment and network managed power strips will then be ordered.
     87Console server equipment and network managed power strips can then be ordered.
    8788The number and type of network managed power strips will depend on whether 110v
    8889or 220v electricity is available and the physical configuration of the cluster
     
    115116SystemImager\footnote{SystemImager - http://www.systemimager.org/} or another
    116117similar software image installation package.  All filesystems should use
    117 \code{ext3} with the obvious exception of of the swap space.
     118\code{ext3} with the obvious exception of system swap space.
    118119
    119120The nodes shall each be assigned a permanent IP address in an RFC
     
    123124to be used for the IPP Cluster then special coordination will need to be made
    124125with the Pan-STARRS Global Systems group due to possible network routing issues
    125 between other PS1 data systems and the IPP Cluster.  The IP address allocation
    126 for the nodes shall be sequentially from the beginning of the address space
    127 with the first two IP address reserved for the gateway.  \tbd{The IP address of
    128 all of the IPP cluster nodes should be recorded into the} \file{/etc/hosts}
    129 file on every node to prevent DNS look-ups during inter-cluster communication.
     126between the IPP Cluster and other PS1 data systems.  The IP address allocation
     127for the nodes shall be sequential from the beginning of the address space with
     128the first two IP address reserved for the gateway.  The IP address of all
     129of the IPP cluster nodes should be recorded into the \file{/etc/hosts} file on
     130every node to prevent DNS look-ups during inter-cluster communication.
    130131\tbd{Additional configuration based on some other document that describes IPP
    131132software requirements?}
     133
     134One of the nodes shall be designated as the centralized log host for Syslog
     135and other monitor tools.  In particular, \code{3DM}\footnote{3DM -
     136http://www.3ware.com/products/raid\_management.asp} shall be used for monitoring
     137the health of the 3ware RAID controllers and attached disks.  \code{3DM} sends
     138warnings and error notifications via SMTP.  The log host should be configured
     139with a dedicated account to receives these messages.
    132140
    133141\begin{figure}
     
    147155\end{figure}
    148156
    149 The IPP Hardware Test Plan (\tbd{separate PSDC number?}) can then begin.  The
    150 testing will cover the following items.
     157The IPP Hardware Test Plan should then be carried out.  The testing will cover
     158at least the following items:
    151159
    152160\filbreak
     
    182190\end{itemize}
    183191
    184 \subsubsection{Stage 2}
     192\subsubsection{Software Development}
    185193
    186194The cluster enters into a period of partial dormancy where all but 6 of the
    187195nodes are deactivated.  The remaining active nodes are to each have 12 disks
    188 from the pool of commissioning disks installed and configured as a single RAID 5
    189 volume mounted as \file{/export/[nodename]/vol0} and exported via NFS as
     196from the pool of commissioning disks installed and configured as a single RAID
     1975 volume mounted as \file{/export/[nodename]/vol0} and exported via NFS as
    190198\code{[nodename]}.  These nodes are to remain available for the testing of IPP
    191199software until the cluster enters into it's production phase.  The duration of
    192 this stage will vary as Stage 3 won't begging until PS1 is almost ready to
    193 start taking data.  The minimum duration of this stage is 2.5 months.
    194 
    195 \subsubsection{Stage 3}
     200this stage will vary as Stage 3 won't begging until PS1 is almost ready for
     201first light.  The minimum duration of this stage is 2.5 months.
     202
     203\subsubsection{Pre-Production}
    196204
    197205The $1^{st}$ lot of storage disks are ordered and the complete cluster is
     
    218226volume mounted as \file{/export/[nodename]/vol0} and shared via NFS by
    219227exporting \file{/export/[nodename]} as \code{[nodename]}.  The new disks shall
    220 then be run through the IPP Storage Test Plan.
     228then be run through the ``Storage'' section of the IPP Hardware Test Plan.
    221229
    222230\begin{figure}
     
    242250
    243251Approximately 6 months after the IPP Cluster enters into the Production phase
    244 the $2^{nd}$ lot of storage disks will need to be ordered.  The new disks shall be
    245 installed in sets of 12 on a single RAID controller in nodes [ipp000..ipp049]
    246 and configured as a single RAID 5 volume mounted as
     252the $2^{nd}$ lot of 600 storage disks will need to be ordered.  It is estimated
     253that by this time the storage capacity will be at least 600B per disk.  The new
     254disks shall be installed in sets of 12 on a single RAID controller in nodes
     255[ipp000..ipp049] and configured as a single RAID 5 volume mounted as
    247256\file{/export/[nodename]/vol1} and exported via NFS as part of the original NFS
    248257sharing of \file{/export/[nodename]}.  The new lot of disks will also need to
    249 be run through the IPP Storage test plan.
     258be run through the ``Storage'' section of the IPP Hardware Test Plan.
    250259
    251260\subsubsection{3rd Disk Lot}
    252261
    253262Approximately 14 months after the IPP Cluster enters into the Production phase
    254 the $3^{rd}$ lot of disks will need to be ordered.  The new disks shall be
     263the $3^{rd}$ and final lot of 600 disks will need to be ordered.  Disk capacity
     264should be at least 900GB per disk by this time.  The new disks shall be
    255265installed in sets of 24 on two RAID controllers in nodes [ipp050..ipp074] and
    256266configured as two RAID 5 volumes (one per controller) mounted as
    257 \file{/export/[nodename]/vol0} \& \file{/export/[nodename]/vol1}.  Both of these
    258 volumes will be shared via NFS by exporting \file{/export/[nodename]} as
    259 \code{[nodename]}.  This lot will also be run through the IPP Storage test
    260 plan.
     267\file{/export/[nodename]/vol0} \& \file{/export/[nodename]/vol1}.  Both of
     268these volumes will be shared via NFS by exporting \file{/export/[nodename]} as
     269\code{[nodename]}.  This lot will also be run through the ``Storage'' section
     270of the IPP Hardware Test Plan.
    261271
    262272\subsection{End of Life}
     
    267277deactivated.  The deactivated nodes shall be stored for possible reuse with
    268278PS4.  This phase will last approximate one year.
     279
     280\section{Maintenance}
     281
     282\subsection{Nodes}
     283
     284The IPP Cluster nodes, excluding data storage disks, will be covered under a 3
     285parts and labor warranty by the OEM.  The significant costs to the Pan-STARRS
     286project will be the labors costs of installation/removal of hardware
     287components, the testing associated with the new hardware components, and
     288possibly the expense of shipping parts back to the OEM.
     289
     290The storage disks, depending on the vendor each lot is purchased from, may or
     291may not be under warranty from the OEM.  In the case that a disk warranty is
     292not extended by the OEM, only disks that are covered under a warranty by the
     293manufacturer will be acquired.  In such a case the Pan-STARRS project will be
     294required to pay the return shipping expenses unless special terms can be
     295negotiated directly with the disk manufacturer.
     296
     297\subsection{Network Equipment}
     298
     299The IPP Cluster core network switch will need to be placed under a
     300SmartNet\footnote{SmartNet -
     301http://www.cisco.com/en/US/products/svcs/ps3034/ps2827/ps2978/serv\_datasheet09186a0080092491.html}
     302contract from Cisco.
     303
     304\tbd{The cost scheduled depends on the level of service contract.}
    269305
    270306\section{Schedule}
     
    295331\includegraphics[angle=-90]{pics/ps1_ipp_cluster_timeline.ps}
    296332}
    297 \caption{ \label{timeline} Timeline}
     333\caption{ \label{timeline} Time-line}
    298334\end{center}
    299335\end{figure}
Note: See TracChangeset for help on using the changeset viewer.