)]}'
{"specs/approved/bmc-settings-management.rst":[{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"a5c7b039f34e3d8d365aa5c4012cf184148e6858","unresolved":true,"context_lines":[{"line_number":18,"context_line":"registry. We don\u0027t expose them today, and we should, but not by pretending"},{"line_number":19,"context_line":"they are BIOS settings. They belong to a different part of the machine and,"},{"line_number":20,"context_line":"more importantly, to a different set of people. This spec proposes managing"},{"line_number":21,"context_line":"BMC settings as their own resource, sitting behind the ``management``"},{"line_number":22,"context_line":"interface, with an access policy that keeps them away from the lessee."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Problem description"}],"source_content_type":"text/x-rst","patch_set":2,"id":"74e6a879_0e1ae04e","line":21,"updated":"2026-09-11 10:44:48.000000000","message":"I wonder if it\u0027s a good point to add a new interface. Management is already overloaded with everything. It does have BMC reset on iDRAC, but it also has boot settings for a System.\n\nI have a somewhat related use case of managing credentials and networking: https://bugs.launchpad.net/ironic/+bug/2162051. These could go as steps on the new interface.\n\nBy the way, do you think networking parameters will be possible to manage through the API you propose?","commit_id":"527244e430166e321b10f3ab29fba326507f2a74"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"a5c7b039f34e3d8d365aa5c4012cf184148e6858","unresolved":true,"context_lines":[{"line_number":51,"context_line":"weaken or lock us out of our own management path. So BMC settings need to be"},{"line_number":52,"context_line":"restricted to the system and to the node\u0027s *owner* administrator, and the"},{"line_number":53,"context_line":"lessee should not see them at all."},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"Use cases:"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* As an owner administrator, I want to audit the current BMC configuration of"}],"source_content_type":"text/x-rst","patch_set":2,"id":"05a96e4c_e7964451","line":54,"updated":"2026-09-11 10:44:48.000000000","message":"Third, a single BMC may manage several nodes. It\u0027s not explicit in your proposed API (we should discuss it too), but at least you highlight that BMC settings are not System settings.","commit_id":"527244e430166e321b10f3ab29fba326507f2a74"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"a5c7b039f34e3d8d365aa5c4012cf184148e6858","unresolved":true,"context_lines":[{"line_number":80,"context_line":"hardware interface. Managing the BMC is part of managing the node, and every"},{"line_number":81,"context_line":"driver that can talk to a BMC already has a ``management`` interface, so we"},{"line_number":82,"context_line":"extend that with optional methods rather than forcing every hardware type and"},{"line_number":83,"context_line":"out-of-tree driver to grow a new interface it would mostly no-op."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Reading and writing are split the same way they are for BIOS. Reading is done"},{"line_number":86,"context_line":"over the REST API with a ``GET``; the values are served from the database,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3afb9f04_15fb28b9","line":83,"updated":"2026-09-11 10:44:48.000000000","message":"Not sure (see above). We already put too much into Management. Also, the new interface will be mostly no-op for IPMI. I\u0027d expect many downstream drivers to inherit Redfish nowadays.\n\nNot a blocking concern, but something to think about.","commit_id":"527244e430166e321b10f3ab29fba326507f2a74"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"a5c7b039f34e3d8d365aa5c4012cf184148e6858","unresolved":true,"context_lines":[{"line_number":95,"context_line":"in one standard place. The generic ``redfish`` ``management`` implementation"},{"line_number":96,"context_line":"reads the attributes carried on the Manager resource itself, via sushy\u0027s"},{"line_number":97,"context_line":"``Manager.bmc``. The ``idrac`` hardware type -- whose management interface"},{"line_number":98,"context_line":"already subclasses the ``redfish`` one -- overrides where it looks and reads"},{"line_number":99,"context_line":"the Dell OEM ``DellAttributes`` resource instead, since that is where iDRAC"},{"line_number":100,"context_line":"keeps them. Either way the sync into ``bmc_settings`` and the"},{"line_number":101,"context_line":"``{\"Attributes\": {...}}`` update used to apply them are the same code, the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"836aa027_6a69079b","line":98,"updated":"2026-09-11 10:44:48.000000000","message":"Aside: I want to kill the iDRAC driver. We already have lots of vendor-specific code in the Redfish one. Dell does not maintain their driver. It\u0027s just a burden on us.","commit_id":"527244e430166e321b10f3ab29fba326507f2a74"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"a5c7b039f34e3d8d365aa5c4012cf184148e6858","unresolved":true,"context_lines":[{"line_number":112,"context_line":"We could add a brand new ``bmc`` hardware interface, mirroring ``bios``. We"},{"line_number":113,"context_line":"rejected this as too much surface area for what it buys. Every hardware type"},{"line_number":114,"context_line":"and every out-of-tree driver would have to declare and usually no-op-implement"},{"line_number":115,"context_line":"the new interface, and we would need new configuration defaults and"},{"line_number":116,"context_line":"enabled-interface lists to go with it. BMC configuration is a natural part of"},{"line_number":117,"context_line":"node management, so a handful of optional methods on ``ManagementInterface``"},{"line_number":118,"context_line":"is the lighter, backwards-compatible path."}],"source_content_type":"text/x-rst","patch_set":2,"id":"a21fd15c_0c1aff60","line":115,"updated":"2026-09-11 10:44:48.000000000","message":"I don\u0027t think this statement is true. A lot of hardware types will (or at least should) inherit from Redfish nowadays, so they\u0027ll get the implementation for free and automatically.","commit_id":"527244e430166e321b10f3ab29fba326507f2a74"}]}