search

vatesfr / xen-orchestra

The global orchestration solution to manage and backup XCP-ng and XenServer.
https://xen-orchestra.com
Other
767 stars 263 forks source link

Initial hardware info on 2CRSi servers #7816

Closed olivierlambert closed 1 month ago

olivierlambert commented 1 month ago

Context

As our partner, we are working with 2CRSi to improve the integration of their hardware into our stack. First thing first, it's about getting more hardware data directly displayed in XO (also URL to the IPMI), giving a great bonus while using a hardware partner vendor. On another issue (in the future), we'll discuss to add extra capabilities, like firmware check and upgrade, and so on.

How

We'll rely on a XAPI plugin to fetch the data, and then parse and interpret them in XO. The plugin output is now like this: https://gist.github.com/olivierlambert/258798cc898d001ef29f77130adef246

Where

No need to make it too complex on the first iteration (especially in XO 5). Since we got a lot of space in host view (default tab), it's likely the right place. We can also add some alerts in the Home/host view in case. More to discuss to create a first iteration.

julien-f commented 1 month ago

I believe the data should be exposed in the REST API.

We should probably add a debounce (delay to decide: 1 min, more?).

How to call the plugin?

olivierlambert commented 1 month ago

Branch is here for this plugin, with the doc: https://github.com/AtaxyaNetwork/xcp-ng-xapi-plugins/tree/ipmi-sensors?tab=readme-ov-file#ipmi-sensors-parser

1min debounce is OK to me.