Description of problem:
ENHANCEMENT: Allow fence_egenera to specify ssh login name. Currently, it only
logs into the cBlade for a fencing operation as the user that ran the script,
and practically speaking, that is always the root user.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The current fence_egenera script logs into the cBlade as root for a fencing
operation. This is preventing a security-conscious client from deploying GFS
clusters in their DMZ environment. Doing SCSI-3 PR in this environment is not
yet a viable option.
Preferably, the default user name for this enhancement would be 'fence', or
something similar. This may or may not cause package update issues. On the
BladeFrame, user 'fence' would have to have rights to the LPAN(s) containing the
servers (and corresponding blades) it needs to be able to fence. This note
would have to be added to the documentation for fence_egenera.
*** This bug has been marked as a duplicate of 349381 ***