is Xo Proxy available in community version

stevewest15

Hi,

Has there been any update on this?

Thx,

SW

hoerup

https://github.com/ronivay/XenOrchestraInstallerUpdater has just added experimental support for provisioning a XO proxy

olivierlambert

The code is entirely open source. It's just that the deploy is exposed in the XOA UI

bogdantomasciuc

Still there is no documented way to deploy a proxy from sources. Is there any plan to document a wy to deploy proxy from sources. I am using a "hacky" version installed from sources but there are constant licensing checks that break functionality and would like to use an installation that is as close to the intented way of functioning as possible.
Also congratulations on an awesome progect!

Pilow

@bogdantomasciuc check https://github.com/ronivay/xenorchestrainstallerupdater
it manages XO Proxies

and ping @acebmxer in the forums who has developped an equivalent

bogdantomasciuc

@Pilow Thanks. I am using that script (Ronivay) but proxy is broken at the moment. Backups complete but the status is failed due to some piece of code that checks for license and returns "Fetch failed". I would like to use a documented albeit unsuported version of xo-proxy without having to comment license checks and the likes.

acebmxer

@bogdantomasciuc

Hello, Yes my script does offer to install xo-proxy and handles some of the licensing issues. You may give my script a try and let me know if you having any further issues i can try to work them out. I advise setting up a new vm for XO as the two script are not compatible that i am aware of.

https://xcp-ng.org/forum/topic/11895/install-xo-from-sources.
https://github.com/acebmxer/install_xen_orchestra/

bogdantomasciuc

@acebmxer Thank you for the reply! I will give it a try installing a new VM and restoring the config from the current VM. Thanx again!

poddingue

That question has come round three times on this thread since 2020, so it isn't a one-off.
I'd rather not promise documentation I can't deliver, but I can take it to the people who decide and come back here either way, including if the answer is that proxy deployment stays an XOA thing.
On the licensing side I'd sooner not encourage patching those checks out, mostly because I don't know what they're guarding.
In the meantime, the two community scripts in this thread are what people are actually running, which is worth saying plainly even though it isn't the documented path you asked for.

bogdantomasciuc

@poddingue Fistst of all I appreciate your answer and your position.
The thing is that, even though the proxy code itself is opensource, the functionality of the plugin is basicaly behind a paywall. We are not talking about support. Actual functioning of the plugin after compiling from sources depends on license availability and there is no option to select no support or something along the lines "I built it myself from sources". Without patching the code even though the proxy is otherwise functional the backups won't work because of missing license. Hopefully the powers that can will provide an acceptable albeit community supported way to use the proxy cleanly, without touching license checks. Best regards!