Build and transfer xo-ce from another machine

Computer Hardware & Server Infrastructure Builds
1

I think the question is simple to understand, but not sure about practicalities.

I use XenOrchestraInstallUpdate Script like lots of others here ( GitHub - ronivay/XenOrchestraInstallerUpdater: Xen Orchestra install/update script ) and it work flawlessly when I give my VM it is running on 4GB. But sometimes I have other VMs running on the host wanting memory so I set my xo-ce to 2 GB, which still functions perfectly for me using it but the updater craps out due to lack of memory if I don’t set it back to 4GB.

I am looking to do the building on another machine and transfer over the final product, set up symlinks to the new folder, and remove the old instance (just like the installer does locally at the moment)

The installer could SSH into another machine from the xo-ce VM if it needed, or else the other machine can just do what it needs to with the xo-ce over SSH.

Is this a silly idea? I just don’t think leaving the xo-ce VM sit on 4GB of RAM when 2GB is enough is a wise use of resources.

I know I can run xo-ce somewhere else but I don’t want that in this case. The other machine will only be spun up when needed.

2

If the goal is to not go through the build process why not use the Docker image from that same script?

1 Like
3

You know I never thought about that and it’s probably the best solution for me. I had been looking at the Docker container for a RPi system I was thinking about using as an emergency backup for xo-ce but never thought about it in this manor.

strikeout

Ok, so a follow up question. With the current VM I’m building it on I could install Docker and run the xo-ce image, and that’s all fine. But, I have docker running already on a VM on the same physical host. Should I keep it separate to that “Docker“ VM or just run it as another container on it?

^ Edit: Nevermind, I do want sepeartion of concerns. Besides I need the VMs on ServerManagementVLAN vs ServersVLAN for me too so separate it is.

Thanks Tom!

1 Like