Thank you for this constructive argument

Have a nice day.

@markhewitt1978 Hi, thank you for your feedbacks!

We are aware that this limitation bothers a lot of users and we have plan to address that in the next major version of XO.

XO 5 was already a major improvement over its predecessor because it allows viewing and handling a much bigger infra.

XO 6 will go further in this direction by introducing a tree view and the possibility to edit and handle many objects at the same time.

@Danp That may not be directly to script but to the external environment: SMB works much better if cifs-utils is installed on the system, something that is present on our doc but might be missing in some install scripts.

We have no animosity whatsoever regarding these scripts but we prefer our appliances (or even manual installs from our documentation) because we understand much better what's going on and it's easier to replicate and fix the issues

Regarding your idea of including the commit identifier for the source version, that's not a bad idea, a (as simple as possible) implementation in a PR would be welcome

@rizaemet-0 Thank you, this is really interesting, it suggest that HTTP encryption in XO is a CPU bottleneck.

It should be alleviated in the future, because in a couple of month, all backup jobs should run in separate process, which will better distribute load on multiple CPUs.

FYI, this feature has been released

I'm thinking about it

Hey everyone!

The patch is finally here

Sorry for the delay

How to test?

1. Select the latest channel on your XO appliance
2. Upgrade to Xen Orchestra 5.43.2
3. Go to the Proxies page and either Deploy a proxy or upgrade the appliance of your existing ones

What's here?

• Full Backup
• Disaster Recovery

Known limitations/issues

Scheduled for Step 2 at the end of the month.

• Network configuration for the proxy appliance
• Delta Backup
• Continuous Replication
• Detailed logs, they are currently empty
• Restoring backups
  Work-around: create a normal remote (not linked to the proxy) connected to the same storage and import via the XO appliance

Thank you for your feedbacks

Indeed, there is a major issue with the fix, I'm on it.

Sorry for this

Answered on the XO forum, thank you

@normanghenderson Yep, it should be coming at the end of the month

We don't to do special cases for some operations in XO 5, we'll revisit this in XO 6 which will bring the notion of XO tasks in addition to XAPI tasks.

But we'll probably display the elapsed and estimated duration of the task though

Regarding previous tasks, why do you need to hide some of them? How do you use these previous tasks?

@busthead If you are importing a VM from your browser, you should not navigate away from XO as it will interrupt the upload. You can navigate to another page of XO though.

@normanghenderson Yep, it should be coming at the end of the month

@kirovtome There is no dedicated param, XO is using the Cloud-init setting ssh_authorized_keys.

@nraynaud ping

@akurzawa @DodgeThis @shorian Any of you able to test this branch to see whether it fixes the issue?

That may indeed be related to a bug lowering the retention, I don't think this occurs with the new backup code, it would be interesting to test once released in xo-server.

You can take a look at this post where I explain succinctly how to check XO backup files

https://github.com/vatesfr/xen-orchestra/commit/1fa42a57538f36583296c63377582422f4a465df

0 julien-f committed to vatesfr/xen-orchestra

chore(xo-server): update hashy to 0.9.0

BREAKING: requires Node >=10.

See https://xcp-ng.org/forum/topic/3107/python3-support

@olivierlambert No, there are no manual procedure available at this time.

@s-pam It's been released ~6 months ago in xoa CLI and in the plugin xo-server-xoa