[ZBXNEXT-3643] please add redfish (an alternative for IPMI) Created: 2017 Jan 04 Updated: 2019 Nov 15 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Trivial |
| Reporter: | Stefan | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 16 |
| Labels: | IPMI, redfish | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
it would be very nice if you add redfish support, that is a more powerfull alternative to IPMI.. |
| Comments |
| Comment by Francine SAUVAGE [ 2019 Sep 07 ] |
|
Please change Priority to Critical now as Redfish is growing : Dell; Intel, IBM, ... and some constructors will soon deliver their products without IPMI for security reason |
| Comment by Stefan [ 2019 Nov 14 ] |
|
since we've http-agent and a powerfull javascript, json thing in zabbix we can do this. I'm working on a template for this |
| Comment by Stefan [ 2019 Nov 15 ] |
|
OK, it looks like that we need ZBXNEXT-1527 for this, because /redfish/v1/Chassis/<ID>/Thermal or /redfish/v1/Chassis/<ID>/Power/PowerSupplies/<ID> is an variable URL because <ID> can change from server to server. So we need nested LLD first to solve this or we create a Template per vendor/server |
| Comment by Francine SAUVAGE [ 2019 Nov 15 ] |
|
Hi @Stefan, I am so happy that you care about Redfish ! I fully agree with you about "variable Urls". I guess /redfish/v1/Chassis/ is a ChassisCollection schema so yes, we need a nested LLD following "Contains" members to obtain the list of Chassis. If you care : I would prefer a solution without agent: http(s) requests could be done remotely by the server without agent, no ? May be on server agent ? Tell me if you need help about Redfish specification, I know much about that standard. Regards, Francine |