Providing software solutions since 1976
FOCUS AREAS
Scalability Community: SAS Grid Architecture
Several types of machines make up a SAS grid environment. These machines have been defined to clarify the software components that must be installed on each one as well as the SAS metadata that must be configured. The SAS Metadata Server installation and configuration should be the first step in the SAS installation, as is typical in a SAS 9 multi-machine install. The machines specific to a grid installation are defined as follows:
-
grid client - a grid client submits work to the grid but is not part of the grid resources available to execute
work. Examples of a grid client include:
- a SAS Data Integration Studio client (Platform LSF not installed on this client machine)
- a SAS Enterprise Miner client (Platform LSF not installed on this client machine)
- a SAS Management Console client using the Schedule Manager plug-in or any other applications scheduling SAS workflows. (Platform LSF not installed on this client machine)
- a SAS foundation install (minimum Base SAS, SAS/CONNECT and Platform LSF) used to run a program that submits work - both whole programs or programs broken into parallel chunks - to the grid. Installation of the Platform LSF component is required in this case in order for SAS/CONNECT to submit the work to the grid.
- SAS Grid Manager client utility - SASGSUB (requires Platform LSF)
- Platform RTM for SAS (requires Platform LSF)
-
SAS Metadata Server - The SAS Metadata Server is shown on a separate machine in this sample architecture. It is common to run the SAS
Metadata Server on a dedicated machine for performance and reliability. If the EGO capabilities of SAS Grid Manager are going to be used to
configure high availability for the SAS Metadata Server, the machine running the SAS Metadata Server must be part of the grid and have LSF
installed on that machine. The most common method for configuring EGO high availability of critical components in the grid is by using a virtual-IP
switch, for example: BIG-IP, Barracuda, or F5. For smaller grid deployments that are primarily using Foundation SAS products, you may choose to run
the SAS Metadata Server on the grid control server. The SAS Metadata Server installation and configuration should be the first step in the SAS installation,
as is typical in a SAS 9 multi-machine install.
-
Platform RTM for SAS - Platform RTM for SAS is a web-based tool that provides IT administrators a way to graphically view the status of devices
and services within their SAS Grid environment as well as manage the policies and configuration of their grid. Platform RTM for SAS is supported on the
following operating systems:
- Red Hat Linux 32/64 bit
- Windows Server 2008 R2 64bit
- Windows 7 32/64 bit
-
Grid Control Server - any machine in the grid can be designated as the grid control server. More software is
installed on the grid control server and more SAS metadata configuration takes place on this machine. You should start
the installation of the Platform Suite for SAS on this machine. In a SAS Data Integration Studio, SAS Enterprise Guide and SAS Enterprise Miner
scenario, for example, the grid control machine runs a workspace server that executes programs that utilize SAS/CONNECT to distribute
work to the grid nodes. The grid control machine can be configured as a grid resource capable of receiving work to
execute or not, depending on the needs of your environment.
- Grid Node - a grid node is a grid computing resource capable of receiving the work that is being distributed. Each grid node must be running a minimum of Base SAS, SAS/CONNECT and Platform LSF.
