Service Card for Login

This is the service card for Login nodes in Phoenix: pub, phoenix1, phoenix2 and ui.

Definition

At the time of writing these lines, there are 4 machines that can be used for login purposes:

• pub is the jump-login node to Phoenix.
• ui is the User Interface that runs the Grid software. From here jobs can be submitted to the cluster.
• phoenix1 and phoenix2 are the main login nodes for sysadmins and from here systems should be monitored and configured (puppet master!).

Other old systems are ui64 (decommissioned) and puppet (still online, but to be decommissioned soon).

Filesystems available are these:

• /home is shared across ui, phoenix1 and phoenix2 (mounted from the NAS appliance)
• /cm is available only on phoenix1 and phoenix2 and it is intended share all the configuration management files required.
• /apps is available on phoenix1 and phoenix2 and contains some benchmarks and monitoring tools that can be used on nodes. This directory is not shared on the rest of the cluster and needs to be mounted on-demand.

Operations

PhoenixN systems

Both phoenixN machines are 'puppetised', while phoenix1 maintains the puppet master tree.

Pub

pub is all local system: no shared FS or any tools are installed here.

Client tools

Testing

Start/stop procedures

Failover check

Checking logs

Set up

Dependencies (other services, mount points, ...)

Redundancy notes

Installation

UI

yum install yum-priorities yum-protectbase
rpm --import http://emisoft.web.cern.ch/emisoft/dist/EMI/3/RPM-GPG- KEY-emi
wget http://emisoft.web.cern.ch/emisoft/dist/EMI/3/sl6/x86_64/base/emi-release-3.0.0-2.el6.noarch.rpm
yum localinstall emi-release-3.0.0-2.el6.noarch.rpm
yum remove voms-clients
yum install emi-ui glite-ce-monitor-cli --enablerepo=epel
yum update --enablerepo=epel
/opt/glite/yaim/bin/yaim -d 6 -c -s /opt/cscs/siteinfo/site-info.def -n UI

Upgrade

Monitoring

Instructions about monitoring the service

Nagios

Ganglia

Self Sanity / revival?

Other?

Manuals

External links to manuals

Issues

Information about issues found with this service, and how to deal with them.

Issue1

Issue2