Install XO from sources.

[dcskinner]

Maybe just semantics, but I have seen here on the boards people ask if they are running XOA or XO from sources. The A means appliance. I think it stops being an appliance if you are managing the OS and installing the app on top of it, so calling this XOA from sources is probably wrong and confusing.

Also, to get full features of XOA, you need to pay for it, so it seems like you are causing confusion with their paid service.

[acebmxer]

@dcskinner

Yes I get what you say about the confusion with XO vs XOA. I know there is another person who maintains an install script calls it XO-CE but didnt want to call mine that specifically.

As for the feature set. You get full feature set when you install from sources. You just dont get paid support.

I have just not implemented the process of setting up a proxy via the script.

Edit - Updated title

[Andrew]

@dcskinner @acebmxer I totally agree.... XOA is the Vates provided software appliance XO system.

Compiling XO yourself is XO from source or XO community edition or anything other than XOA. Calling it XOA adds confusion because it's not the same thing that Vates provides.

[acebmxer]

I appreciate the comments and they are all welcome. Do keep note that I did say this is not Production ready and use at your own risk. If you see anything that is wrong please provide suggest feedback to correct said issue.

I just started running my home lab from this version yesterday. I imported my config from previous XO. Today i saw 4 new commits and the update function updated to the latest commit. Backups have run with no issue.

As I can only test in my home lab I can only speak of my own experiences.

[acebmxer]

Just added the option for --proxy to deploy xo proxy.

https://github.com/acebmxer/install_xen_orchestra/tree/xo-proxy

Deploying a Proxy VM
The script supports deploying a Xen Orchestra Proxy VM directly to your XenServer/XCP-ng pool using the --proxy option:

./install-xen-orchestra.sh --proxy

Important Limitations and Notes

️ Network Configuration:
The --proxy option does not allow you to specify which network the VIF is attached to
It will default to "Pool wide network associated with eth0"

️ Production Use Warning:
Use at your own risk. Not advised for use in production environments.

This feature is provided for testing and development purposes. For production deployments, it is recommended to manually configure proxy VMs with proper network planning and validation.

While can add host and remote via proxy. Backups will fail with the following error.

backupNg.runJob
{
  "id": "95ac8089-69f3-404e-b902-21d0e878eec2",
  "schedule": "76989b41-8bcf-4438-833a-84ae80125367"
}
{
  "code": -32000,
  "data": {
    "stack": "TypeError: licenses.find is not a function
    at Function.<anonymous> (file:///usr/local/lib/node_modules/@xen-orchestra/proxy/app/mixins/appliance.mjs:168:23)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at file:///usr/local/lib/node_modules/@xen-orchestra/proxy/app/mixins/backups.mjs:110:25"
  },
  "message": "licenses.find is not a function"
}

[Pilow]

@acebmxer @ronivay stumbled upon this too
https://github.com/ronivay/XenOrchestraInstallerUpdater#backup-proxy

Backup proxy
Proxy installation method is experimental, use at your own risk. Proxy installation from sources is not documented by Xen Orchestra team. Method used here is the outcome of trial and error.

Proxy source code will be edited slightly to disable license check which only works with official XOA and there is no documented or working procedure to bypass it properly (there used to be but not anymore)

[acebmxer]

@Pilow

Yeah i was looking over his script to see how he worked around it but just states that.

I knew there would be limitations with it so i didnt add it to the main branch yet.

[acebmxer]

@pilow

As I am completly new to this scripting and such I did reach out to Ai for assistance and believe the license check should be bypassed now.

Again not suggested to use in production. Use at your own risk.

still has its own branch for more testing before merging to main branch.

[acebmxer]

https://github.com/acebmxer/install_xen_orchestra

Made some improvements to the script including a inter active menu that will show commit for the script itself compared to the master commit. (should relected which branch you run the script from) With Xen Orchestra Commit comparison and show the Node version installed. The script should self update on launch.

Always review code before using. Use in production at your own risk.

Always open to ideas and suggestions.

  ╔══════════════════════════════════════════════════════════════════════════════════╗
  ║              Install Xen Orchestra from Sources Setup and Update                 ║
  ╚══════════════════════════════════════════════════════════════════════════════════╝

                        Current Script Commit : 693f4
                        Master Script Commit  : 693f4
                        Current XO Commit     : a1b2c
                        Master XO Commit      : d4e5f
                        Current Node          : v24.1.0

  ──────────────────────────────────────────────────────────────────────────────────

  ▸ [✓] Install Xen Orchestra                   [ ] Reconfigure Xen Orchestra
    [ ] Update Xen Orchestra                    [ ] Rebuild Xen Orchestra
    [ ] Rename Sample-xo-config.cfg             [ ] Edit xo-config.cfg
    [ ] Install XO Proxy

  ──────────────────────────────────────────────────────────────────────────────────

  Selected: 1

  ↑↓←→ Navigate   SPACE Select/Deselect   ENTER Confirm   Q Quit

[Greg_E]

@acebmxer

I haven't tried this yet, but liking the menu you just showed!