XOA From The Sources Update Help

planedrop

Wanted to get a little input here so I had a full understanding. I currently run XOA compiled from source on Ubuntu for my homelab so I can test features before deploying new versions at work (we pay for the top license).

However, I have 2 main questions about this:

How do I easily tell which version of XOA I am running since it's not listed in the XOA Update section when building from the sources?
Secondly, how do I update to the newest versions? I've followed the update section here: https://xen-orchestra.com/docs/installation.html#from-the-sources But so far I'm not seeing the newest features such as OVA exporting

I'll admit I'm not the most experienced when it comes to compiling stuff from source, so if these are obvious questions I apologize.

karlisi

@planedrop To avoid confusion, XOA is paid product, ready to use virtual application. If you installed XO from sources, it's simply XO or XOCE (XO Community Edition). XO components versions you can see in About menu, both xo-server and xo-web. If you want to know how it corresponds to XOA version, see changelog https://github.com/vatesfr/xen-orchestra/blob/master/CHANGELOG.md

olivierlambert

On the sources, you are ideally only on the latest commit from master. So you are always more in a more recent than XOA (which is released once a month).

planedrop

@karlisi OK this helps a ton.... I have NO idea how I forgot about the About section of XO lol, my bad.

I guess what I'm confused about is that I'm using it from the sources but don't have the export as OVA feature (or the snapshots coalescing section of the health dashboard). So it would seem I'm not on the newest version, but I can see I'm on xo-server 5.74.1 and xo-web 5.77.0.

planedrop

@planedrop To be clear, I also have the free version of XOA running on this box, and it reports xo-server as 5.93 and web as 5.96.

So the sources one is behind, which makes me think my sources one isn't updating correctly when I go through the instructions.

olivierlambert

Indeed. On recent version of the sources, the version of xo-web/xo-server doesn't really matter and it's not dislayed. That's why you have this now: https://xen-orchestra.com/docs/community.html#current-version

As you correctly reported, if you still see it, it means you are not up-to-date

Go in your xen-orchestra folder, and you can do a git log to see the latest commit on top. 2 reasons you might be outdated:

not being on latest commit via git (git pull)
not doing any rebuild since the git pull

planedrop

@olivierlambert So I did a git log and checked, I'm seeing the latest commits like I should be. Ran git pull --ff-only, then yarn, then yarn build. But after all that I end up on the same version of XO, seems like it's basically not updating.

Might just build a new VM and start from scratch, seems I messed something up along the way a while back.

olivierlambert

The usual errors in that case:

you are not rebuilding the "right" folder (the XO you see in your browser is not the one you are rebuilding)
you can just remove the XO folder and re-git clone and rebuild in doubt, no need to rebuild the whole VM

planedrop

@olivierlambert Well, you were right, I was totally in the wrong folder without realizing it. However, after the rebuild it now won't start at all.

Rebuilding the VM and restoring config is easy though (thanks to XO being so easy to use) so I might just do that to avoid confusion as this VM has some other issues unrelated to XO anyway.