Bug 1476929

I think we should include the process like we do in the other sections and then link to the full DOC for further info:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/administration_guide/#Setting_fencing_parameters_on_a_host

Here is an example of what I think section 2.2 should look like:

Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
Click Edit to open the Edit Host window.
Click the Power Management tab.

Figure 7.2. Power Management Settings
Select the Enable Power Management check box to enable the fields.
Select the Kdump integration check box to prevent the host from fencing while performing a kernel crash dump.
IMPORTANT
When you enable Kdump integration on an existing host, the host must be reinstalled for kdump to be configured. See Section 7.5.12, “Reinstalling Hosts”.
Optionally, select the Disable policy control of power management check box if you do not want your host's power management to be controlled by the Scheduling Policyof the host's cluster.
Click the plus (+) button to add a new power management device. The Edit fence agent window opens.

Figure 7.3. Edit fence agent
Enter the Address, User Name, and Password of the power management device.
Select the power management device Type from the drop-down list.
NOTE
For more information on how to set up a custom power management device, see https://access.redhat.com/articles/1238743.
Enter the SSH Port number used by the power management device to communicate with the host.
Enter the Slot number used to identify the blade of the power management device.
Enter the Options for the power management device. Use a comma-separated list of 'key=value' entries.
Select the Secure check box to enable the power management device to connect securely to the host.
Click the Test button to ensure the settings are correct. Test Succeeded, Host Status is: on will display upon successful verification.
WARNING
Power management parameters (userid, password, options, etc) are tested by Red Hat Virtualization Manager only during setup and manually after that. If you choose to ignore alerts about incorrect parameters, or if the parameters are changed on the power management hardware without the corresponding change in Red Hat Virtualization Manager, fencing is likely to fail when most needed.
Click OK to close the Edit fence agent window.
In the Power Management tab, optionally expand the Advanced Parameters and use the up and down buttons to specify the order in which the Manager will search the host's cluster and dc (datacenter) for a fencing proxy.
Click OK.
You are returned to the list of hosts. Note that the exclamation mark next to the host's name has now disappeared, signifying that power management has been successfully configured.
####

ex.
Address: rhs-srv-05-mm.gdev.lab.eng.rdu2.redhat.com
User Name: root
Password: calvin
Type: drac7
Port: [blank]
Slot: [blank]
Options: [blank]

Thanks for reporting, Dave.

This content is actually managed by the Gluster team, so I'm moving this bug over to their queue for review.

Moving this again to the correct product queue to enable review.

Looks good to me.

Thanks,
Dave

Hi Laura,

  I see that in section 2.2 there is a link to 'Reinstalling Hosts' and that link does not have information to deploy HostedEngine on the hosts while reinstalling which is a crucial step.

Thanks
kasturi

Laura, i think for now we can ask them to follow steps from i to v in the Important Note under 9.3 section.

Laura, sure. Let us add it as another section then which says 'reinstalling hosts'

Hi Laura,

   The doc content in the links provided in comment 18 looks good to me. But when i click on the link 'Reinstalling Hosts' it says 404 error not found. Does this get fixed automatically when the docs are live ?

Thanks
kasturi

Cool, Thanks laura.

Verified in the links provided in comment 18 and as suggested by laura changed the link to access.qa.redhat.com and the link works fine.