NPACI Rocks Cluster Tool Kit 5.1 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News NPACI Rocks Cluster Tool Kit 5.1 (Default branch)
# 1  
Old 11-19-2008
NPACI Rocks Cluster Tool Kit 5.1 (Default branch)

Rocks is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters. Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users). Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation. License: BSD License (revised) Changes:
Enhancements and updates were made to all packages. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

CentOS 6.8 with Rocks Cluster: ldconfig is not a symbolic link errors

Any help appreciated just logging in to this server which is a front end for Rocks Cluster 6.1.1. Getting the below errors: ldconfig ldconfig: /usr/lib/libX11.so.6 is not a symbolic link ldconfig: /usr/lib/libjpeg.so.62 is not a symbolic link ldconfig: /usr/lib/libpng12.so.0 is not a symbolic... (3 Replies)
Discussion started by: RobbieTheK
3 Replies

2. Linux

Rocks cluster 6.1 and MPICH2 problem??????

Hey friends, I am trying to execute a simple hello world in mpi on MPICH2 on Rocks cluster. here is the c source code. #include <mpi.h> #include <stdio.h> int main( int argc, char ** argv ) { MPI_Init( NULL, NULL ); int world_size; MPI_Comm_size( MPI_COMM_WORLD, &world_size ); ... (4 Replies)
Discussion started by: gabam
4 Replies

3. Linux

Intermittent connectivity issues with ROCKS on a compute cluster

I have a cluster set up with a head node and compute nodes running TORQUE and MOAB. The distro is ROCKS 5.3. I've been having problems with the connectivity for the past couple weeks now. Every couple hours it seems like the network connectivity will just stop working: sometimes it'll start back up... (0 Replies)
Discussion started by: gandalf85
0 Replies

4. UNIX for Advanced & Expert Users

Need Help installing a Computational Tool Kit

Hi ! I have been trying to install IMSL Computational Tool Kit on a server. It is a Lunix Redhat V.4 with Intel pentium d processor and Intel fortran compiler 8.1 and the type of command shell we run is bash. I dont know if the problem is with the Installation or the Lunix system. I have... (1 Reply)
Discussion started by: dsmv
1 Replies

5. Cybersecurity

Coroner's Tool Kit for HPUX?

Does anyone know the locacation of a version of the "Coroner's Tool Kit" or other utility for HP-UX 10.20 which can reconstruct files deleted by mistake but not backed up? Thanks (1 Reply)
Discussion started by: bs6
1 Replies
Login or Register to Ask a Question
PACEMAKER(8)						  System Administration Utilities					      PACEMAKER(8)

NAME
Pacemaker - Part of the Pacemaker cluster resource manager SYNOPSIS
crm_node command [options] DESCRIPTION
crm_node - Tool for displaying low-level node information OPTIONS
-?, --help This text -$, --version Version information -V, --verbose Increase debug output -Q, --quiet Essential output only Stack: -A, --openais Only try connecting to an OpenAIS-based cluster -H, --heartbeat Only try connecting to a Heartbeat-based cluster Commands: -n, --name Display the name used by the cluster for this node -N, --name-for-id=value Display the name used by the cluster for the node with the specified id -e, --epoch Display the epoch during which this node joined the cluster -q, --quorum Display a 1 if our partition has quorum, 0 if not -l, --list Display all known members (past and present) of this cluster (Not available for heartbeat clusters) -p, --partition Display the members of this partition -i, --cluster-id Display this node's cluster id -R, --remove=value (Advanced) Remove the (stopped) node with the specified name from Pacemaker's configuration and caches In the case of Heartbeat, CMAN and Corosync 2.0, requires that the node has already been removed from the underlying cluster Additional Options: -f, --force AUTHOR
Written by Andrew Beekhof REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org Pacemaker 1.1.10-29.el7 June 2014 PACEMAKER(8)