This is very different and that might explains it Add @florent in the loop

Hi,

We need a bit more context. What kind of backup exactly? XOA or XO sources? Which version?

Let me ping @Team-XO-Frontend

Why not using anti affinity with the load balancer? This way, you can have multiple groups of VMs that won't run at the same place

What do you mean by "unreadable"? Can you be more specific?

Also, more is coming to XO 6 progressively, we'll be on par this year. About /v5 by default, we documented it IIRC.

Ping @Team-XO-Backend

@pilow the doc in GH repo is meant for XO sources, not XOA. It's up to us to integrate this in XOA, one way or another.

Let me ping @Team-XO-Backend

Hi,

Not sure to get it, XOA isn't meant to be tinkered. Why would you add an npm package on it?

Ping @gregoire

Ping @Team-XO-Backend

Ping @Team-XO-Backend

Pinging @Team-OS-Platform-Release

Most of the team is at the Xen Spring Meetup, they will come back here next week

Reping @Team-Hypervisor-Kernel

Adding @Team-XO-Backend in the loop

Nice catch @vagrantin !

Feel free to open a new thread if you have other problems.

Hi,

Thanks for the report. Adding @Team-XO-Backend in the loop!

Different use cases: Ceph is better with more hosts (at least 6 or 7 minimum) while XOSTOR is better between 3 to 7/8.

We might have better Ceph support in the future for large clusters.

I think I added it after the video ^^ (between the recording and the official release)

Hi!

It's great to never miss a release blog post, because most of the time, we answer many questions there already

https://xen-orchestra.com/blog/xen-orchestra-6-3/#️-security

Okay waiting for your feedback