But but nothing with the current XAPI plugin, so that might need to modify it.

Yes, sorry I have the BMC IP, but not inlet nor outlet temp, I will check why you don't have total power.

edit: in the sensor data you sent, I don't have any total power available

I'm afraid those data aren't complete enough for SuperMicro: I have no BMC info (no IP address), no inlet or outlet temp. It's probably because it's not a full chassis but just info from the motherboard?

For Supermicro, you can use the following branch olt-supermicro-ipmi and tell me if you have anything displayed in the host view.

You can provide:

xe host-call-plugin host-uuid=<uuid> plugin=ipmitool.py fn=is_ipmi_device_available

Then if yes:

xe host-call-plugin host-uuid=<uuid> plugin=ipmitool.py fn=get_all_sensors

And paste the result here, with a markdown code block syntax please

Hi!

1. Yes, as usual for each LTS node version, it's expected to become fully compatible
2. You are already on the sources, so there's no guarantee of stability. Might be interesting to provide feedback if you have issues, helping everyone and making us fix bugs sooner

@Cyrille is back next week

Have you read the link I've sent? It explains exactly the reasons and answer your question

You can imagine that if we have hundreds of 3rd party scripts, each doing their own way to install, it means we'll have to de facto support them all, despite it's unrelated to Xen Orchestra itself. Which means spending resources instead of working on Xen Orchestra directly (or fixing XO bugs).

That's why it's preferable to open a ticket in the Github repo of the script creator, because that's exactly there you'll find the right answer, and also making sure the script creator could even fix their scripts if needed.

If you need community support in here, you have to install it by following the official documentation: https://docs.xen-orchestra.com/installation#from-the-sources

Also adding @thomas-dkmt in case we need to update the doc to make it clearer

Hi,

XOA is only the name of the commercial product. You are using XO from the sources.

As stated in the documentation (with a BIG yellow warning), if you have an issue with a 3rd party script, you should create an issue in their repo.

https://docs.xen-orchestra.com/community

So first, it's not an XO issue, which helps to diagnose it. Then, it might be a subtle XCP-ng bug indeed.

Hi,

We don't have any Super micro server to test it so far. We are discussing with them so it might change in the future.

For HPE, I can take a look, we have few machines.

Can you reproduce the issue with xe CLI?

Order doesn't matter

Question for @florent or @Bastien-Nollet

So we probably need to tell XO team the "right way" to enable HA because there's no way to know from "outside"

I think @florent fixed some timeout things very recently. Please update to latest commit now and try again

Can you start this host? If it's online, XAPI can't tell if it's really off or maybe disconnected from the management but still connected to the shared storage and creating a potential data corruption.

Hi,

A question between @dinhngtu and the @Team-OS-Platform-Release I suppose

Nice!! Happy to see more tools coming on top of our REST API!