Bug 2008584

Summary: [RFE] Redfish API in Ironic for Power Management
Product: Red Hat OpenStack Reporter: Julia Kreger <jkreger>
Component: openstack-ironicAssignee: OSP Team <rhos-maint>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: pweeks, sbaker
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Julia Kreger 2021-09-28 15:32:34 UTC
One of the difficulties to adopting ironic, especially in the style of deployments utilized by the Mass Open Cloud, is the fact few other deployment tools support Ironic as a backend. In part because ironic owns the lifecycle and workflow, where as most other deployment tools are focused on *just* deployment. Adding in a variable of use models such as ownership delegation, and this becomes even harder since the great advantage of BMaaS is delineation of access controls so BMC credentials don't need to be shared or revealed outside of the BMaaS service owner.

The contributors at MOC/RH Research have an answer to this, offer a redfish API interface to manage the power state of a machine without revealing credentials, to ultimately allow end users to use their existing redfish supporting tools to request power state changes on a baremetal node.

It should be noted, this was previously raised as an IPMI interface, however we do not ship the intermediate required library to do that nor do we really want usage of IPMI to continue given IPMI has fundamental security issues in it's design, where as Redfish is a much more modern and capable interface.

Comment 1 Julia Kreger 2022-10-04 20:02:45 UTC
Looks like this has stalled upstream. The contributor working in this area did last revise the patch a few months ago.