It might be nice to let users specify the cluster ID in Conga. This parameter is an attribute of the cman element in cluster.conf. Example: <cman cluster_id="1234"/> This attribute is completely optional. If it is not explicitly defined, cman will generate one based on the cluster name. However, when using scsi reservations as a fence method, it is *recommended* that you explicity define a unique cluster ID. The reason is that this value is used to generate unique scsi reservation keys. By combining cluster ID and node ID we can generate a unique reservation key for each node. cluster_id (in C) is a 16-bit value, if that matters. So its max value would be 65535 (0xFFFF hex), in case Conga does any range checks.
What happens if the cluster is already running, and a user happens upon this form field, and decides they want to put their phone number in the cluster ID field for fun...will suddenly changing the cluster ID param in the conf file break anything?
Yes. Just like changing your node IDs would break your scsi reservation keys. Changing either your cluster ID or node IDs while you have existing reservations/registrations is a bad idea.
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request.