beautypg.com

1 overview of the user environment, System architecture, Hp xc system software – HP XC System 3.x Software User Manual

Page 19: Operating system, Node platforms

background image

1 Overview of the User Environment

The HP XC system is a collection of computer nodes, networks, storage, and software, built into a cluster,
that work together. It is designed to maximize workload and I/O performance, and to provide the efficient
management of large, complex, and dynamic workloads.

This chapter addresses the following topics:

System Architecture (page 19)

User Environment (page 23)

Application Development Environment (page 24)

Run-Time Environment (page 24)

Components, Tools, Compilers, Libraries, and Debuggers (page 26)

System Architecture

The HP XC architecture is designed as a clustered system with single system traits. From a user perspective,
this architecture achieves a single system view, providing capabilities such as the following:

Single user login

Single file system namespace

Integrated view of system resources

Integrated program development environment

Integrated job submission environment

HP XC System Software

The HP XC System Software enables the nodes in the platform to run cohesively to achive a single system
view. You can determine the version of the HP XC System Software from the /etc/hptc-release file.

$ cat /etc/hptc-release

HP XC x3.0

bl3 20050805

Operating System

The HP XC system is a high-performance compute cluster that runs HP XC Linux for High Performance
Computing Version 1.0 (HPC Linux) as its software base. Any serial or thread-parallel applications, or
applications built shared with HP-MPI that run correctly on Red Hat Enterprise Linux Advanced Server Version
3.0, also run correctly on HPC Linux.

Node Platforms

The HP XC System Software is available on several platforms. You can determine the platform by examining
the top few fields of the /proc/cpuinfo file, for example, by using the head command:

$ head /proc/cpuinfo

Table 1-1

presents the representative output for each of the platforms. This output may differ according to

changes in models and so on.

System Architecture

19