Bug 1478354 - [Docs][Tech][Admin] Add suggestion to use specific power management agent instead of common ipmilan
[Docs][Tech][Admin] Add suggestion to use specific power management agent ins...
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: ovirt-4.1.6
: ---
Assigned To: Byron Gravenorst
Depends On:
  Show dependency treegraph
Reported: 2017-08-04 08:13 EDT by Martin Perina
Modified: 2018-03-06 06:59 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Docs
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Perina 2017-08-04 08:13:46 EDT
Description of problem:

As mentioned in BZ1455502 customers should use specific fence agent for their servers instead of common ipmilan agent, because those concrete power management agents contains default options which are optimized for modern servers, while ipmilan agent may require to override default option to use with modern servers. For example:

 HP servers
   - use ilo4/ilo3

 Dell servers
   - use drac5 or idrac

 IBM servers
   - use imm

Is it possible to mention this recommendation in Technical Reference Guide [2] and maybe it's also worth to insert link mentioning [2] inside Configuring Host Power Management Settings chapter in Administration Guide [1].

[1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/sect-host_tasks#Configuring_Host_Power_Management_Settings
[2] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/technical_reference/power_management

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Note You need to log in before you can comment on or make changes to this bug.