Building Linux cluster for mechanical engineering software Post: 302918888

Sponsored Content

Special Forums UNIX and Linux Applications High Performance Computing Building Linux cluster for mechanical engineering software Post 302918888 by Don Cragun on Friday 26th of September 2014 03:34:02 AM

09-26-2014

Registered User

Some of your questions are so vague that it is hard to make any informed suggestions. How would you respond if you got a request from someone to tell them how to choose the best vehicle? (Who is going to be driving it? How many passengers do you need to carry? How much weight do you need to be able to tow? How much secured cargo space do you need? What are the weather conditions where it will be driven? What type of terrain does it need to traverse? ...)

I know very little about about ME and nothing about Ansys CFD. Are you trying to build a cluster to support hundreds of users submitting thousands of jobs? Are you trying to build a cluster than can break a single huge job into thousands of threads and run all of those threads simultaneously? Do you have any experience writing thread-safe code?

Can you use only open-source software? Of course you can! You can write all of the code you need and make it available for everyone to use as they see fit.

Does open-source software already exist for all of the code you want to run? How can we guess at that from what you've told us? We have no idea what all of the code you want to run needs to do.

If you don't know the difference between a heterogeneous cluster and a homogeneous cluster, you probably don't have the background needed to design the cluster you want. Please consider hiring an architect with experience setting up and running an HPC data center who you can sit down with and discuss budget, capabilities, computing projects to be run, users to be supported, software to be run, software to be written, etc., etc., etc. Setting up an HPC data center is a very complex, expensive undertaking.

Don Cragun

View Public Profile for Don Cragun

Find all posts by Don Cragun

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

building and running a software in different linux kernel versions

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.

2. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More...

3. High Performance Computing

Building a Linux Virtual Server cluster

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...

4. Red Hat

Free Cluster software with Red Hat Linux 5.0

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.

LEARN ABOUT DEBIAN

ditrack

DITRACK(1)						      General Commands Manual							DITRACK(1)

NAME

       dt - DITrack command line client tool

SYNOPSIS

       dt command [options] [args]
       dt-createdb repository-url issue-db-dir local-wc
       dt-upgrade-0.7-db issue-db-dir

OVERVIEW

       DITrack	is a free, open source, lightweight, distributed issue (bug, defect, ticket) tracking system using a Subversion repository instead
       of a backend database. It is written in Python and runs in UNIX environment (*BSD, Linux, MacOS X).

       The project is inspired by the idea of Subissue issue tracking system.

       However, while Subissue aims in merely replacing the traditional database storage with Subversion repository, DITrack is a major  rethought
       of  the	issue  tracking  system  paradigm. The main difference is that instead of sticking to the centralized model (one database, one web
       interface, one mail integration machinery), DITrack treats underlying Subversion storage as  a  versioned  distributed  file  system  which
       enables benefits of truly distributed operation mode.

       For more information about the DITrack project, visit http://www.ditrack.org.

       Documentation  for  DITrack  and  its  tools,  including  detailed  usage  explanations of the dt and dt-createdb programs, can be found at
       /usr/share/doc/ditrack/html/index.html.

       Run `dt help' to access the built-in tool documentation.

       Automatic upgrade is possible for databases created by DITrack 0.7. If you are upgrading from previous version of DITrack, use the  upgrage
       utility from DITrack 0.7 first.

       To upgrade a database run the dt-upgrade-0.7-db script, passing the database path as the argument, like:

       dt-upgrade-0.7-db /home/user/ditrack-database

       The  upgrade  procedure	merely	modifies the working copy (nothing gets committed to the repository). So, when done, you should commit the
       changes manually.

								    April 2007								DITRACK(1)