Topics created by olivierlambert

@olivierlambert the new wiki is Oh là là

Excellent job, thanks! I will enjoy reading this, to see if it will teach me anything new about XCP-ng.

great work an gratulations I am gulty loaed more than one times

yea, that's exactly what I was wondering. I'm curious how it was done. I was thinking of doing something similar for my ELK cluster and a few other systems.

For now, all you get in the webhook request are the API call parameters and result (and a few other things). This is a generic behaviour that doesn't depend on what the call does. If you need some more specific information, your webhook handler can, for example, make a call to XO's API to fetch that information.

@borzel Thanks, excited to be here!

Issue is now fixed. You can clearly see IOwait exploding during the storage network issue:

Ubuntu LTS

Always

Thanks for your input! I think it might be the one then Also, if there is a big problem with it, we can always update the package!

@stormi dd stands for disk dump and does exactly that: Copy a stream of data. Fio however can be configured for precise workloads and read/write mixes, parallel workloads etc. So the first thing will only give you streamline benchmarks, what almost nobody cares about. The second can simulate realworld (VM/database...) workloads, where (controller) Caches and non magnetic storage (Flash, Optane, MRAM...) makes the real difference. Also use big amount of data, since caches can impact small ones extremely. Don't get me wrong: We need them and they can make huge differences, but as long as your benchmarks fully fit into them, it gives your nonsense/fake results. Also (consumer) SSDs start throttling after some 10 to a very few 100 GB of data written. Their caches fill up and they 'overheat'. You can spend days on benchmarks and how to do what.

Cert is renewed... the proxy didn't reload after cert renewal...

Yes so on a low frequency CPU, stunnel is indeed a bottleneck. It's far less the case on CPU with higher clock

Nicely done!

This is what we use (xenstore) for XOA deploy. However, Cloudinit is almost a de facto standard, so we think it's better to use it than custom scripts.