sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-03-09 08:58:35 +03:00
Code

convert rest of pages to new format

Browse Source 
(This used to be ctdb commit c111fb4fdfbc657bc715337003febbd0313870d1)
This commit is contained in:
Andrew Tridgell 2007-06-08 14:35:26 +10:00
parent d523c48d6d
commit b925e9e668
5 changed files with 40 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
ctdb/web/building.html
View File

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Building CTDB and Samba</TITLE>
<TITLE>CTDB</TITLE>
</HEAD>
<BODY BGCOLOR="#ffffff" TEXT="#000000" VLINK="#292555" LINK="#292555" ALINK="#cc0033">
<!--#include virtual="header.html" -->
<h1>Building CTDB and Samba</h1>
<H2 align="center">Building CTDB and Samba</h2>
<h2>CTDB</h2>
To build a copy of the CTDB code you should do this:
@ -35,5 +35,4 @@ Once compiled, you should install Samba on all cluster nodes.<br><br>
The /usr/src/ctdb path should be replaced with the path to the ctdb sources that you downloaded above.
</BODY>
</HTML>
<!--#include virtual="footer.html" -->

48
ctdb/web/configuring.html
View File

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Configuring CTDB</TITLE>
<TITLE>CTDB</TITLE>
</HEAD>
<BODY BGCOLOR="#ffffff" TEXT="#000000" VLINK="#292555" LINK="#292555" ALINK="#cc0033">
<!--#include virtual="header.html" -->
<h1>Configuring CTDB</h1>
<H2 align="center">Configuring CTDB</H2>
<h2>Clustering Model</h2>
@ -13,37 +13,43 @@ The setup instructions on this page are modelled on setting up a cluster of N
nodes that function in nearly all respects as a single multi-homed node.
So the cluster will export N IP interfaces, each of which is equivalent
(same shares) and which offers coherent CIFS file access across all
nodes.<br><br>
nodes.<p>
The clustering model utilizes IP takeover techniques to ensure that the full set of public IP addresses assigned to services on the cluster will always be available to the clients even when some nodes have failed and become unavailable.
The clustering model utilizes IP takeover techniques to ensure that
the full set of public IP addresses assigned to services on the
cluster will always be available to the clients even when some nodes
have failed and become unavailable.
<h2>CTDB Cluster Configuration</h2>
These are the primary configuration files for CTDB.<br>
When CTDB is installed, it will install template versions of these files
which you need to edit to suit your system.<br>
The current set of config files for CTDB are also available from http://samba.org/~tridge/ctdb/config
These are the primary configuration files for CTDB.<p>
When CTDB is installed, it will install template versions of these
files which you need to edit to suit your system. The current set of
config files for CTDB are also available from
<a href="http://samba.org/~tridge/ctdb/config">http://samba.org/~tridge/ctdb/config</a>
<h3>/etc/sysconfig/ctdb</h3>
This file contains the startup parameters for ctdb.<br>
This file contains the startup parameters for ctdb.<p>
When you installed ctdb, a template config file should have been installed in /etc/sysconfig/ctdb.<br>
When you installed ctdb, a template config file should have been
installed in /etc/sysconfig/ctdb.<p>
Edit this file, following the instructions in the template.<br><br>
Edit this file, following the instructions in the template.<p>
The most important options are:
<pre>
* CTDB_NODES
* CTDB_RECOVERY_LOCK
* CTDB_PUBLIC_INTERFACE
* CTDB_PUBLIC_ADDRESSES
</pre>
<ul>
<li>CTDB_NODES
<li>CTDB_RECOVERY_LOCK
<li>CTDB_PUBLIC_INTERFACE
<li>CTDB_PUBLIC_ADDRESSES
</ul>
Please verify these parameters carefully.
<h4>CTDB_RECOVERY_LOCK</h4>
This parameter specifies the lock file that the CTDB daemons use to arbitrate
which node is acting as a recovery master.<br>
@ -51,6 +57,7 @@ This file MUST be held on shared storage so that all CTDB daemons in the cluster
You <strong>must</strong> specify this parameter.<br>
There is no default for this parameter.
<h3>CTDB_NODES</h3>
This file needs to be created and should contain a list of the private IP addresses that the CTDB daemons will use in your cluster. One ip address for each node in the cluster.<br>
@ -154,5 +161,4 @@ We recommend that you use public ip addresses using CTDB_PUBLIC_INTERFACE/CTDB_P
You may also wish to setup a static WINS server entry listing all of your cluster nodes IP addresses.
</BODY>
</HTML>
<!--#include virtual="footer.html" -->

9
ctdb/web/download.html
View File

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Getting the code</TITLE>
<TITLE>CTDB</TITLE>
</HEAD>
<BODY BGCOLOR="#ffffff" TEXT="#000000" VLINK="#292555" LINK="#292555" ALINK="#cc0033">
<!--#include virtual="header.html" -->
<h1>Getting the code</h1>
<H2 align="center">Getting the code</h2>
You need two source trees, one is a copy of Samba3 with clustering patches, and the other is the ctdb code itself.<br>
@ -50,5 +50,4 @@ If you don't have bzr and can't easily install it, then you can instead use the
rsync -avz samba.org::ftp/unpacked/samba_3_0_ctdb/ .
</pre>
</BODY>
</HTML>
<!--#include virtual="footer.html" -->

2
ctdb/web/header.html
View File

@ -17,7 +17,7 @@ style="margin-top: 0">
<td align="left">
<ul>
<li><small><a href="http://wiki.samba.org/index.php/CTDB_Setup">wiki</a></small>
<li><small><a href="bugzilla.html">bug-tracking</a></small>
<li><small><a href="http://bugzilla.samba.org/">bug-tracking</a></small>
</ul>
</td>
</tr>

11
ctdb/web/testing.html
View File

@ -1,14 +1,12 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Starting and testing CTDB</TITLE>
<TITLE>CTDB</TITLE>
</HEAD>
<BODY BGCOLOR="#ffffff" TEXT="#000000" VLINK="#292555" LINK="#292555" ALINK="#cc0033">
<!--#include virtual="header.html" -->
<h1>Starting and testing CTDB</h1>
<H2 align="center">Starting and testing CTDB</h2>
<h2>Starting and testing CTDB</h2>
The CTDB log is in /var/log/log.ctdb so look in this file if something diud not start correctly.<br><br>
Log in to all of the nodes in the cluster and start the ctdb service using
@ -91,5 +89,4 @@ response from 2 time=0.000114 sec (17 clients)
response from 3 time=0.000115 sec (59 clients)
</pre>
</BODY>
</HTML>
<!--#include virtual="footer.html" -->