[h3]How to move the services manually, to the secondary node (candy):[/h4]
This will also prevent the resource to automatically failover if the primary node is back online so keep that in mind when you plan several reboots on primary node and you don't want to be bothered.
crm resource migrate nfs-group candy
How to stop/start a resource group:
crm resource stop nfs-group
crm resource start nfs-group
One way to modify the cluster crm configuration:
crm configure edit
At this point, you will be introduced in "vi mode" and you can edit anything you want. Do not forget to save exit afterwards. Once done, continue with:
commit exit
How to add another DRBD volume in the existing cluster configuration:
1. Add new resource:
primitive drbd_squid ocf:heartbeat:Filesystem \
params fstype="reiserfs" directory="/nfs/squid" device="/dev/drbd1" \
meta target-role="Started"2. Teach the cluster to mount the filesystems in the right order (drbd_fs is mounting the /nfs partition so it must be started first):
order drbd_fs-before-drbd_squid mandatory: drbd_fs:promote drbd_squid:start colocation drbd_squid-on-drbd_fs inf: drbd_squid drbd_fs:Master
3. Edit drbd_main and add nfsquid to drbd_resource:
primitive drbd_main ocf:heartbeat:drbd \
params drbd_resource="nfs [color=red]nfsquid[/color]" \
op monitor interval="59s" role="Master" timeout="30s" \
op monitor interval="60s" role="Slave" timeout="30s"4. Add the new ressource to the existing nfs group:
group nfs-group drbd_fs [color=red]drbd_squid[/color] nfs_server nfs_common nfs_ip
How to restart service within the cluster:
Once you add something in cluster configuration, it is advisable to stop/start it only within the cluster.
So, if you want to (let's say) restart nginx server, you will have to do it with heartbeat commands:
# crm resource restart <service>
If you want to just reload, you can do it the classic way but make sure the configuration is OK because otherwise the cluster will detect the failure and will fail-over the service to the other node (on which will fail too since you have the same "wrong" configuration).
Example:
root@eave:~# crm resource restart nginx_srv
INFO: ordering nginx_srv to stop
INFO: ordering nginx_srv to start
root@eave:~# crm_mon -1 | grep nginx_srv
nginx_srv (lsb:nginx): Started eaveroot@eave:~# /etc/init.d/nginx configtest Testing nginx configuration: nginx. root@eave:~# /etc/init.d/nginx reload Reloading nginx configuration: nginx.
