Description of problem:
Conga creates cluster.conf files w/o enforcing the definition of a fencing
device - the user is able to modify the file after it's creation, but by
default, the user is not required to define a fencing device

Version-Release number of selected component (if applicable):
luci-0.8-25.el5
ricci-0.8-25.el5

How reproducible:
100%

Steps to Reproduce:
1. Create a new cluster via Conga
2. When the nodes are rebooted, the cman service starts on all the nodes, then
tries to fence some members, this fails (in a 3-node cluster, it fails on one
node) - that node is blocked 
  
Actual results:
The user has to modify the cluster.conf file - this can be done via Conga - to
reference a fencing device.

Expected results:
The user should be required to specify a fencing device - so that when a cluster
is created in Conga, it comes up and is fully functional by default.

Additional info:

Here's an example cluster.conf file as generated by Conga:

------------------------------------------------
<?xml version="1.0"?>
<cluster alias="testCluster" config_version="1" name="testCluster">
        <fence_daemon post_fail_delay="0" post_join_delay="3"/>
        <clusternodes>
                <clusternode name="tng3-2.lab.msp.redhat.com" nodeid="1" votes="1"/>
                <clusternode name="tng3-3.lab.msp.redhat.com" nodeid="2" votes="1"/>
                <clusternode name="tng3-4.lab.msp.redhat.com" nodeid="3" votes="1"/>
        </clusternodes>
        <cman/>
        <fencedevices/>
        <rm/>
</cluster>
------------------------------------------------