Date: Wed, 26 Jun 2002 12:32:13 +0800 From: derekbarrett@graffiti.net To: Andy Sporner <sporner@nentec.de>, freebsd-cluster <freebsd-cluster@FreeBSD.ORG> Subject: Re: Early documentation- Message-ID: <20020626043213.30513.qmail@graffiti.net>
next in thread | raw e-mail | index | archive | help
This documentation seems pretty strong at this point. Here are some areas where I think I can contribute: 1. Overall description of the cluster architecture, a general overview of how its mechanisms work 2. A link or brief instructions on how to make sure source code is available for libkvm, ps, and top. 3. Examples of an rc startup script 4. HTML formatting of the instructions, for public posting (with the maroon and yellow FreeBSD "style") I'm sure I will have more to add after running the installation, but at this point it seems to have all the major elements needed. Derek ----- Original Message ----- From: Andy Sporner <sporner@nentec.de> Date: Tue, 25 Jun 2002 13:39:25 +0200 To: freebsd-cluster <freebsd-cluster@FreeBSD.ORG> Subject: Early documentation- > Here is some very poor documentation for those early adoptors among us. > Derek is going to > be working on better documentation, so this is only interrim... > > Andy > > Content-Type: text/plain; name="docset.txt" > Installing basic cluster software: > > 1. Obtain and install the CSE patch if your system is FreeBSD. > 2. Download the latest cluster source code. > Place in current directory > 3. unzip the archive with the 'gunzip' command. > 4. Un-TAR the archive with 'tar xvf phase1-???-src.tar' > 5. Change directories to phase1. > 6. Start the build of the software with 'make'. > 7. The resultant software is located in /tmp/buildpkg. > Change directories there. > 8. Start the install process with ./inst.cluster > > During the build process, a tar file is created in ~phase1/binaries. For > machines with the same machine architecture (and OS version) this file > be used instead of going through a complete build process on each machine. > Un-TAR this file and start from step 8 above. > > It is up to the system administrator to integrate the startup of the > cluster software into the system startup. > > Installing CSE Patch: > > For best results, the source code should be available for libkvm, ps, and top. > > 1. Unpack the patch file. > 2. Enter the directory and type 'make'. > > During this process, various source files are modified within 'ps'. It will > be necessary to rebuild libkvm, top and ps. Note that PS now displays the > app id during it's default output in the second column. > > II CONFIGURATION: > > Once the cluster software is loaded, start the daemon by the following > command: > > clusterd > > This will cause the load of the cluster modules and start all other > subtasts. > > Before this it might be necesarry to tune the cluster daemon. This is > done by modifying the file '/usr/local/cluster/etc/cluster.conf'. There > are various tunable options there. > > Now the configuration of the cluster can begin. In order to do this, > start the cluster configuration GUI. This is done by invoking 'cl_admin'. > NOTE: it is necesary that 'clusterd' is running on the local node where > cl_admin is running. > > Two areas are present, 'resources' and 'nodes'. > > First create the names of all of the nodes of the cluster. This is > done by right-clicking on the heading 'nodes' and selecting 'NEW'. The > name should either match the hostname of the machine or the override > name specified in 'cluster.conf' for that machine. > > Then for each node under the "LLI" heading, right click to add each > network interface IP address that specifies the new node (Really this > *MUST* be an IP addresss--not a dns name). When all have been added, > the resources need to be added. > > Right click on the 'resources' heading and select new. Enter a name > for the resource and it's weight (that is how much of the machine > will it utilize). The weight is used to schedule failover of applications. > The monitor will never schedule applications where their weight cannot > be allocated. It a resource becomes too large, it can be rescheduled > to another node. Autostart allows a resource to start right away when > the cluster starts initially. > > The name of the resource should be a legal filename since it will > have a corresponding script in /usr/local/cluster/etc/rc.d. The script > will recieve two possible parameters: 'start' and 'stop', which cause > the resource to be started or stopped, respectively. For IP address > failover configure a 'zero' weight and for the start option the ifconfig > option to bring up the address and for the stop option the command > to bring down the interface. For other things model the script like > an standard 'rc' script. There is an example script in > /usr/local/cluster/lib directory. > > To add nodes to the resources, drag either the resource over the node, > or the node over the resource. > > Control of any of the objects on the configuration screen can be done > with a right-click. > > To start the cluster software into active mode: (IE: this is what should > be in the RC script) type 'cluster start'. The current running status > can be returned by 'cluster status'. To stop the cluster, enter > 'cluster stop'. > > > > > > > > > > > > > -- _______________________________________________ Get your free email from http://www.graffiti.net Powered by Outblaze To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-cluster" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020626043213.30513.qmail>