Editing SAMBA CLUSTER PUNJAB GOVT IFMS-IWDMS PROJECT (section)

== CTDB Configuration  ==
The CTDB configuration file is located at /etc/sysconfig/ctdb. The mandatory fields that must be configured for CTDB operation are as follows: 

• CTDB_NODES 

• CTDB_PUBLIC_ADDRESSES 

• CTDB_RECOVERY_LOCK 

• CTDB_MANAGES_SAMBA (must be enabled) 


The following is our configuration file for CTDB operation: 


CTDB_RECOVERY_LOCK="/mnt/ctdb/.ctdb.lock" 

CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses 

CTDB_MANAGES_SAMBA=yes 

CTDB_MANAGES_WINBIND=no 

CTDB_NODES=/etc/ctdb/nodes 

CTDB_DEBUGLEVEL=ERR 


The meaning of these parameters is as follows. 


CTDB_NODES 

Specifies the location of the file which contains the cluster node list. 


The /etc/ctdb/nodes file that CTDB_NODES references simply lists the IP addresses of the cluster nodes, as in the following example: 

192.168.10.81 

192.168.10.82 


CTDB_PUBLIC_ADDRESSES 

Specifies the location of the file that lists the IP addresses that can be used to access the Samba shares exported by this cluster. These are the IP addresses that you should configure in DNS for the name of the clustered Samba server and are the addresses that CIFS clients will connect to. 


The contents of the /etc/ctdb/public_addresses file on node1 is: 

192.168.10.93/0 eth1 


And node 2: 

192.168.10.93/0 eth0 


CTDB_RECOVERY_LOCK 

Specifies a lock file that CTDB uses internally for recovery. This file must reside on shared storage such that all the cluster nodes have access to it. We use the GFS2 file system that will be mounted at /mnt/ctdb on all nodes. This is different from the GFS2 file system that will host the Samba share that will be exported. This recovery lock file is used to prevent split-brain scenarios. 


CTDB_MANAGES_SAMBA 

When enabling by setting it to yes, specifies that CTDB is allowed to start and stop the Samba service as it deems necessary to provide service migration/failover. 

When CTDB_MANAGES_SAMBA is enabled, you should disable automatic init startup of the smb daemons by executing the following commands: 

<nowiki># chkconfig smb off </nowiki>


CTDB_MANAGES_WINBIND 

When enabling by setting it to yes, specifies that CTDB is allowed to start and stop the winbind daemon as required. 


The smb.conf configuration file must be identical on all of the cluster nodes. We will modify the file when we integrate it with 389-DS.


After starting up the cluster, you must mount the GFS2 file systems that you created. The permissions on the Samba share directory and user accounts on the cluster nodes should be set up for client access.