12-22-2008
After DustBunny's (valuable and how true...)comments, my 2 cents:
Having lived with different clusters on different platforms, I believe a good and well built and architectured box is less trouble than a cluster ( a box able to crash and reconfigure itself by removing faulty HW...) and almost as fast if not faster than an average cluster...
A well tuned and efficient cluster is different of course, but as DustBunny will confirm - It takes quite some time and skill, by highly qualified personnel...
You just cant follow a procedure to put up a cluster, theres rarely 2 same clusters doing the same thing...
What can you do?
Urgently follow the "Hand-on MSSG" course so you have a good idea what you are being asked!
By following the course, you will get material knowledge and worksheets for you to start to fill with all the prerequisites you will have for your cluster..
Then start to play with the software to see you understand how it works (what you need to get it running) like make yourself a little apache server with read/write webdav and a few WWW authenticated users, and TEST throughly before trying less obvious (oracle DB...) once you are confident with the commands and updates procedure of your simple cluster, go for the big challenge!
It takes, to understand a cluster, the same time to learn UNIX administration (not administering it just understand and not being lost when the gurus come along and modfiy things...) so what do you expect by asking for procedures?
Because of the price of a cluster, you just cant improvise and hope it will work, it is going to ask you quite some investment
The help that can be given to you here is our experience, we can help you putting up your cluster by discussing which architecture is most suitable or by giving you feed back on what we have been through with such configuration, most probably help you sort out with something you are unhappy about with your cluster...
Most valuable advise I can give you:
Remember what UNIX is all about!
So courage my friend and warn your family you will spend less time with them for a couple of weeks for you need to study...
5 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I'm exploring a few different careers( Unix System's Admin, Network Engineer, and Unix System's Engineer). I asked in another thread about System's Admin, so I have some more info on that already. I'm not finding very much info on Network Engineers or Unix System Engineers though. Can you guys... (0 Replies)
Discussion started by: hpicracing
0 Replies
2. UNIX for Dummies Questions & Answers
Like many UNIX users, there is a small team that is connected to UNIX (under the same UNIX user) via putty from a Windows PC.
Is there a way, once under UNIX, to know the address of the originating computer or anything that can differentiate initial users ? (7 Replies)
Discussion started by: popescu1954
7 Replies
3. Shell Programming and Scripting
How do I create a shell script called 'custinfo' to prompt a customer to enter and display back the following: name, age, address, phone number, product, price range.
Thanks (1 Reply)
Discussion started by: SQLScript
1 Replies
4. UNIX for Dummies Questions & Answers
reposting
How do I create a shell script called 'custinfo' to prompt a customer to enter and display back the following: name, age, address, phone number, product, price range.
Thanks (1 Reply)
Discussion started by: SQLScript
1 Replies
5. Shell Programming and Scripting
Need a perl script that will extract component reference designators from a text file and write them to a new file. The refdes attribute will always follow the characters "REFDES=". So for the first line below I'd like to extract the reference designator R2402.
A 2158 1882 12 2 2 3... (5 Replies)
Discussion started by: jeffs123456
5 Replies
LEARN ABOUT CENTOS
sasl_server_step
sasl_server_step(3) SASL man pages sasl_server_step(3)
NAME
sasl_server_step - Perform a step in the authentication negotiation
SYNOPSIS
#include <sasl/sasl.h>
int sasl_server_step(sasl_conn_t *conn,
const char *clientin,
unsigned clientinlen,
const char ** serverout,
unsigned * serveroutlen);
DESCRIPTION
sasl_server_step() performs a step in the authentication negotiation. It returns SASL_OK if the whole negotiation is successful and
SASL_CONTINUE if this step is ok but at least one more step is needed.
conn is the SASL connection context
clientin is the data given by the client (decoded if the protocol encodes requests sent over the wire) clientinlen is the length of cli-
entin
serverout and serveroutlen are set by the library and should be sent to the client.
RETURN VALUE
sasl_server_step returns an integer which corresponds to one of the SASL error codes. SASL_CONTINUE indicates success and that there are
more steps needed in the authentication. SASL_OK indicates that the authentication is complete. All other return codes indicate errors and
should either be handled or the authentication session should be quit.
CONFORMING TO
RFC 4422
SEE ALSO
sasl(3), sasl_errors(3), sasl_server_init(3), sasl_server_new(3), sasl_server_start(3)
SASL
10 July 2001 sasl_server_step(3)