Xen Orchestra proxies - Test Feedback
-
Your proxy was deployed in a DHCP enabled env, right?
-
Yes the DHCP server give an IP to the proxy
-
Good thanks
I think we got a patch coming very soon, done by @julien-f fixing this error
-
Okay, thanks. I'm waiting for the patch.
If I'm not in DHCP I have the same problem as the other users, a timeout and the proxy is deleted.
-
Hey everyone!
The patch is finally here
Sorry for the delay
How to test?
- Select the
latestchannel on your XO appliance - Upgrade to Xen Orchestra 5.43.2
- 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
- Select the
-
@Franck-Leclerc feel free to try again now
-
Thanks for the update.
I can now backup a VM with the proxy
I continuing my tests
-
Great thanks!
-
Are proxies an XOA-restricted feature? If yes, then the GUI should indicate that and prevent you from attempting to deploy when built from source. If no, then this functionality is still broken (
TypeError: app.getResourceCatalog is not a function) when built from source.
-
Proxies are like XOA (or XO Hub templates): they are pre-configured appliances hosted on xen-orchestra.com, explaining why you can only deploy them from XOA.
However, you should be able to use the sources to register a proxy yourself, but we'll document that later (it's still in dev and code is moving fast).
Anyway, we'll expose that in the UI, thanks for the feedback
