Migrating a Client to XCP-ng – Stability of the Community Edition?
-
Hello everyone,
I have a client who recently ordered a new physical server infrastructure along with a SAN. They are currently running two CentOS hosts that haven’t been updated in five years. Given their strong preference for open-source solutions (they are a higher education institution), I’m considering migrating them to XCP-ng.
My initial plan is to deploy the fully open-source version of XCP-ng (Community Edition) to allow them to test the platform for about a year before potentially moving to the paid version at the end of 2025.
My main questions are:
1. Is the Community Edition stable enough for production use in this type of environment?
2. Has anyone here deployed the free version in a similar scenario, and what were your experiences?
3. Are there any key limitations in the Community Edition that might impact long-term adoption before transitioning to a paid plan?The primary goal is to ensure a smooth migration and provide them with a reliable solution while staying within their open-source philosophy. Any insights or recommendations would be greatly appreciated!
Thanks in advance!
-
@Cygace as far as i know xcp-ng in general is open-source and works the same as the paid version. The paid version does only apply to support and maintenance based on the Xen Orchestra Appliance XOA which is a paid product. However you can run XOA from sources with the same functionality as the paid version. The only thing u will miss is the support from the Vates Team, i believe in a production environment it's always preferable to run paid support but for testing purpose i see no reason why not to start with the unpaid versions.
-
- Yes, works great if you pick a stable, known good version (commit).
- See #1 as long as you deploy it correctly.
- No Vates support, no support tunnel, no click to update, no xostore, no quick help on issues.
- You are tech support.
-
@Andrew How to find the good version in 8.3 ?
-
@Cygace XO is not directly tied to XCP. So the versions have nothing to do with each other.
You can look at the XO master commits and pick one that lists feat: release 5.xxx.x and that will line up with a XOA release. You can pick a version that is the same as the current XOA release and it will be the same tested base code.