DescriptionSirius Rayner-Karlsson
2017-06-26 09:16:59 UTC
1. Description:
Feature request to include a Redfish API fence-agent RHEL7
2. Details
a. Bugzilla dependencies (if any):
Unknown
b. Hardware dependencies (if any):
Intel RackScale Design based hardware that complies with RedFish API 1.0 specification
c. Upstream information
i. Date it will be upstream:
There is the Sushy work, that is a library for interacting with RedFish API, but that is not a fencing agent.
ii. Version:
Unknown
d. External links:
N/A
e. Severity (U/H/M/L):
High
f. Business Priority (Must/High Want/Want):
Must
3. Business Justification
a. Why is this needed:
As RSD systems are becoming more common, having a fencing agent that handles RedFish API is becoming a necessity. Hardware from several vendors will implement and leverage RedFish instead of IPMI. Enabling RHEL to be used in a HA capacity on this kind of hardware is a priority.
b. What hardware is required (if any):
Any hardware of Intel RackScale Design type that implements RedFish API 1.0 for system management and remote service interface.
c. Business impact:
Lack of generic fence agent for RedFish API will slow adoption of Intel's RackScale Design based hardware for Red Hat Enterprise Linux in an HA capacity (which also affects products like OpenStack and others that leverage hardware fencing for some features).
Comment 8Oyvind Albrigtsen
2018-12-07 12:35:02 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:2037
1. Description: Feature request to include a Redfish API fence-agent RHEL7 2. Details a. Bugzilla dependencies (if any): Unknown b. Hardware dependencies (if any): Intel RackScale Design based hardware that complies with RedFish API 1.0 specification c. Upstream information i. Date it will be upstream: There is the Sushy work, that is a library for interacting with RedFish API, but that is not a fencing agent. ii. Version: Unknown d. External links: N/A e. Severity (U/H/M/L): High f. Business Priority (Must/High Want/Want): Must 3. Business Justification a. Why is this needed: As RSD systems are becoming more common, having a fencing agent that handles RedFish API is becoming a necessity. Hardware from several vendors will implement and leverage RedFish instead of IPMI. Enabling RHEL to be used in a HA capacity on this kind of hardware is a priority. b. What hardware is required (if any): Any hardware of Intel RackScale Design type that implements RedFish API 1.0 for system management and remote service interface. c. Business impact: Lack of generic fence agent for RedFish API will slow adoption of Intel's RackScale Design based hardware for Red Hat Enterprise Linux in an HA capacity (which also affects products like OpenStack and others that leverage hardware fencing for some features).