Softpanorama
May the source be with you, but remember the KISS principle ;-)

Contents Bulletin Scripting in shell and Perl Network troubleshooting History Humor

Cluster Tools (C3)

Cluster Command & Control (C3) tool suite

News Enterprise Unix System Administration Recommended Links c3.conf cpush cexec cget  crm
Environment Parallel command execution Cluster SSH pssh Slurping Tentakel parallel Mussh
  Unix Configuration Management Tools rdist rsync  SSH Power Tool Perl Admin Tools and Scripts Grid Engine Unix System Monitoring
SSH Usage in Pipes Password-less SSH login scp sftp Tips History Humor Etc

One of the problems with Cluster management software is that they try to put you some framework which might not what you want. So trying to help they overshoot and became a nuisance.  This is especially true about commercial software where complexity serves as protection from competitors. Often you need a tool that provides the necessary functionality, but at the same time allows to use it as a building block for your own more complex scripts. In this case you need something different form all-singing all dancing commercial tools.

So this is an area where open source tools have a chance.

The Cluster Command and Control (C3) tool suite is such open source tool (set of Python scripts, downloadable from C3 Software ). It was developed for use in operating the HighTORC Linux cluster at Oak Ridge National Laboratory.

C3 tools package includes seven commands/scripts. All of them require ssh access to the nodes. Of them three are really valuable:

  1. cpush - push a file across cluster
  2. cexec - execute any command on each cluster node
  3. cget - get a file across cluster

And other four are marginally valuable

  1. crm - delete files or directories across cluster
  2. cshutdown - shutdown command for cluster nodes
  3. ckill - kill process across cluster
  4. cpushimage - push disk image across cluster

There are also three management commands

  1. clist - lists name and type of all clusters in the cluster configuration file
  2. cname - returns a node position from a node name
  3. cnum - returns a node name from a node position

There are four common options (each command has also command specific options)

Tools are controlled by a configuration file which can be specified as a parameter -f. Default is /etc/c3.conf. For example

cluster rhel {
	rhbox1 # head node 
	centos[1-6] # compute nodes
}
cluster sles {
	us0[1-7]
}
cluster solaris {
	mail[1-3]
	dns[1-2]
}

The first cluster in the file is called default cluster similar to the first declaration in a Makefile. Any instance of a C3 command that does not explicitly name the cluster executes on the first cluster in the configuration file.

The first cluster in the file is called default cluster similar to the first declaration in a Makefile. Any instance of a C3 command that does not explisidly name the cluster executes on the first cluster in the configuration file.

Cluster configuration file should consist of one or more cluster descriptor blocks: syntactic objects that name and describe a single cluster that is accessible to that system's users. The following is an example of a default configuration file that contains exactly one cluster descriptor block: a block that describes a cluster of 64 nodes:

cluster rhel { 
	htorc-00:node0 #head node 
	node[1-64] #compute nodes 
} 

Cluster description blocks consist of the following basic elements:

In the current version of the C3 tool set range values are treated as numbers, with no leading zeroes. A declaration like

node[01-64] #compute nodes 

Expands to node1, node2,... node64, not to node 01, node01,..., node64.

To specify a set of nodes with names like node01, node09, node10, ...node64, use declarations like

cluster local { 
   htorc-00:node0 #head node 
   node0[1-9] #compute nodes node01..node09 
   node[10-64] #compute nodes node10..node64 
} 

There can be multiple clusters defined in the c3.conf. For example: 

cluster local { 
orc-00:node0 #head node 
node[1-64] #compute nodes 
exclude 2 
exclude [55-60] 
} 

cluster torc { 
:orc-00b 
} 

cluster my-cluster { 
osiris:192.192.192.2 
woody 
dead riggs 
}
The first cluster in the file is called default cluster and is used if not cluster name is specified in the command.
Top updates

Bulletin Latest Past week Past month
Google Search


NEWS CONTENTS

Old News ;-)

Example of the usage of cexec command

cexec 'yum -q -y install ntp'

Recommended Links

 



Etc

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes.   If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. 

ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.  

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least


Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.

The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Last modified: March, 17, 2017