09-25-2014
Building Linux cluster for mechanical engineering software
Hello everybody,
I'm new here in the forum and first i will greet everybody.
Also I'm new with the issue of HPC, but I have to inform my urgently.
My issue:
I'm a mechanical engineer, specialised on simulation like fluid dynamics (CFD) and FEM. Especially I'm programming software for this case.
Everyone who knows CFD, knows already which resources such a simulation needs. In the past I worked on a workstation (Dual-Core Xeon E5), but now I have to build a cluster, especially which can manage the jobs in different queues.
My requirements:
- It should be a linux cluster
- I want to build a cluster with some (for the beginning two) dual-core xeon servers, more machines will follow soon.
- For the special software tools (Ansys CFD) a clone of rhel 6.3 (scientific linux 6.5 is already working) is necesarry.
- For the user GUIs (meshing for CFD or monitor the simulation) a X-Server, which is available by rdp or/and NX, is needed
- For the software I build on my own, I will take experience with GPGPU- and MPI - Programming (not so important, this issue can wait)
I think that are the important values for the Cluster. For that issue I had searched a long time, but I don't found many information about hpc-cluster building and I don't found good literature therefor.
Because of that my questions:
- Are there a good HowTo to build those cluster ?
- Which (special) hardware do I need ?
- Which software do I need for all that (user administration, parallel filesystem, batch system to manage the jobs, cluster-monitoring, MPI, ...) ?
- Can I use only open-source software ?
- Should I use a VM with another linux as base?
I know these are many questions, but I don't find another way and the time is running out.
I'm very happy about every helpful answer. I want to thank you in advance!!
Greets
Last edited by biro; 09-25-2014 at 06:32 PM..
4 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
my Querry is
if i build a software on a specific linux kernel
and then try to run it on another linux kernel
....what can be the possible problems
or what errors can most probably appear while running the binary in an updated version of linux. (1 Reply)
Discussion started by: mobydick
1 Replies
2. High Performance Computing
Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
3. High Performance Computing
Hi Guys,
I'm busy building a LVS-NAT cluster on Red-Hat server 5.1 and I need a kernel that has LVS capabilities for a red-hat server 5.1. Is the anyone who can advise me where I can get this kernel. I have already visited the following site Ultra Monkey: and this has old kernels e.g. 2.4.20... (2 Replies)
Discussion started by: Linux Duke
2 Replies
4. Red Hat
Hi,
I would like to know wheather any free cluster software is coming with Red Hat Ent Linux Medias? or needs to be purchased seperately. (3 Replies)
Discussion started by: manoj.solaris
3 Replies
LEARN ABOUT OPENSOLARIS
scds_syslog_debug
scds_syslog_debug(3HA) Sun Cluster HA and Data Services scds_syslog_debug(3HA)
NAME
scds_syslog_debug - write a debugging message to the system log
SYNOPSIS
cc [flags...] -I /usr/cluster/include file -L /usr/cluster/lib -l dsdev
#include <rgm/libdsdev.h>
void scds_syslog_debug(int debug_level, constchar *format...
DESCRIPTION
The scds_syslog_debug() function writes a debugging message to the system log. It uses the facility returned by the scha_cluster_getlogfa-
cility(3HA) function.
All syslog messages are prefixed with: SC[<resourceTypeName>,<resourceGroupName>,<resourceName>,<methodName>
If you specify a debug_level greater than the current debugging level being used, no information is written.
The DSDL defines the maximum debugging level, SCDS_MAX_DEBUG_LEVEL, as 9. The scds_initialize(3HA) function, which the calling program must
call before scds_syslog_debug(), retrieves the current debugging level from the file: /var/cluster/rgm/rt/<resourceTypeName>/loglevel.
Caution -
Messages written to the system log are not internationalized. Do not use gettext() or other message translation functions in conjunction
with this function.
PARAMETERS
The following parameters are supported:
debug_level Debugging level at which this message is to be written. Valid debugging levels are between 1 and SCDS_MAX_DEBUG_LEVEL,
which is defined as 9 by the DSDL. If the specified debugging level is greater than the debugging level set by the
calling program, the message is not written to the system log.
format Message format string, as specified by printf(3C)
... Variables, indicated by the format parameter, as specified by printf(3C)
EXAMPLES
Example 1 Display All Debugging Messages
To see all debugging messages for resource type SUNW.iws, issue the following command on all nodes of your cluster
echo 9 > /var/cluster/rgm/rt/SUNW.iws/loglevel
Example 2 Suppress Debugging Messages
To suppress debugging messages for resource type SUNW.iws, issue the following command on all nodes of your cluster
echo 0 > /var/cluster/rgm/rt/SUNW.iws/loglevel
FILES
/usr/cluster/include/rgm/libdsdev.h
Include file
/usr/cluster/lib/libdsdev.so
Library
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscdev |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
printf(3C), scds_syslog(3HA), scha_cluster_getlogfacility(3HA), syslog(3C), syslog.conf(4), attributes(5)
Sun Cluster 3.2 7 Sep 2007 scds_syslog_debug(3HA)