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

ghi

GHI(1)							      General Commands Manual							    GHI(1)

NAME

       ghi - command-line interface to the GitHub Issues API

SYNOPSIS

       ghi command [arguments] [options]

DESCRIPTION

       This manual page documents briefly the ghi command.

       ghi is a command-line interface to the GitHub Issues API. It can be used to access all of GitHub's documented Issues API (v2) functionality
       from the command line: open, close and manipulate issues.
       If no command is given, the default action is list. If a number is given instead, the default action is show.

COMMANDS

       list [ -s open|closed|all ]
	      Show open, closed or all issues (choose with -s, see below). Default is open.

       show number
	      Show issue number. This command can be invoked also as ghi <number>.

       open [ number ], o [ number ]
	      Create a new issue, and launch $EDITOR. If number is given, reopens that issue.

       open -m message, o -m message
	      Create a new issue with message content (optionally, use 
 for new lines; first line will be the issue title).

       close number, c number
	      Closes issue number.

       edit number, e number
	      Edit issue number with $EDITOR.

       label add|remove label number
	      Add or remove label to/from issue number.
	      You can use al or rl instead of, respectively, label add and label remove.

       search term, s term
	      Search for term.

       comment number, m number
	      Create a comment for issue number (with $EDITOR).

OPTIONS

       -h, --help
	      Show summary of options.

       -v, --verbose
	      Show issue details (only for show, list and search commands). Default is false.

       -V, --version
	      Show program's version number and exit.

       -s STATE, --state=STATE
	      Specify state (only for list and search (except "all") commands). Choices are: open (o), closed (c), all (a). Default is open.

       -r REPO, --repo=REPO, --repository=REPO
	      Specify a repository. The format: "user/repo" or just "repo" (latter will get the user from the global git config).

       -w, --web, --webbrowser
	      Show issue(s) GitHub page in web browser (only for list and show commands). Default is false.

AUTHOR

       github-cli was written by Sander Smits <jhmsmits@gmail.com>.

       This manual page was written by David Paleino <dapal@debian.org>, for the Debian project (and may be used by others).

								  April 13, 2010							    GHI(1)