Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng
-
@john.c correct. It's the auto updates and automations that come with the appliance that I am after. I believe the trial is only one month? Or possibly only 15 days? The support element is mostly irrelevant to me/us. I do a fair bit of automation via Ansible/Terraform, so developing our own unique library of Templates is ideal. Again, new to all this. So, it may just be that I've not come across this within my XO from "sources" build.
To your point - I was referring to XO Community = to XO Sources.
We may be unique in our internal policies to test for min 9-12 months prior to subscription? Proxmox licensing worked very well for us, because even when our three node HA edge cluster was in production, we were still able to license per the lowest tier which mad the whole stack so much more financially viable. I think we have 2/3 nodes on basic licensing and 1 may even be on Community! We are very technically savvy bunch that has managed to get by on this thus far.
Thanks for the comments/feedback. Much appreciated!
-
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c correct. It's the auto updates and automations that come with the appliance that I am after. I believe the trial is only one month? Or possibly only 15 days? The support element is mostly irrelevant to me/us. I do a fair bit of automation via Ansible/Terraform, so developing our own unique library of Templates is ideal. Again, new to all this. So, it may just be that I've not come across this within my XO from "sources" build.
To your point - I was referring to XO Community = to XO Sources.
We may be unique in our internal policies to test for min 9-12 months prior to subscription? Proxmox licensing worked very well for us, because even when our three node HA edge cluster was in production, we were still able to license per the lowest tier which mad the whole stack so much more financially viable. I think we have 2/3 nodes on basic licensing and 1 may even be on Community! We are very technically savvy bunch that has managed to get by on this thus far.
Thanks for the comments/feedback. Much appreciated!
@cichy Though do note that you can make your case to Vates staff, during the trial if you find you donât have enough time to test. Just donât string them along by gaming the trial offer, to the point it becomes of infinite length, in a similar fashion to another organisation which wonât be named.
Also Netdata is a valuable plugin available in the appliance version of Xen Orchestra (XOA). A useful part of any monitoring solution.
The updating functionality in Xen Orchestra has recently gained the capability to be scheduled to run regularly. Finally in the last couple of months, Vates has completely re-done the backup feature in Xen Orchestra. If your workplace operates in regulated industry or policies are for air gapped infrastructure then Vates have most definitely got you covered with Pro and Enterprise plans!!
The XO Hub feature is only available to the appliance version as it is tied, to the Vates IT infrastructure. As well as likely the user account. Another feature present in the appliance version is the capacity for your Xen Orchestra settings, to be synchronised against the Vates account!
You may be very technically minded and/or your team, but as you state your new to the Vates VMS stack. Your access to their paid support, through the subscription support plan will pay for itself. Additionally your supporting (funding) future work on the software Vates releases. They can help you track down issues, as developers and thus root out what causes problems. Plus as members of the Xen Project and through that Linux Foundation, this will likely prove valuable - influence on future development.
If you pay yearly and sufficient multiple years, youâll have the following based on choice made:-
- 1 Year - No Savings
- 3 Years - Up to 10% Savings in 3 years
- 5 Years - Up to 15% Savings in 5 years
Check the comparison between the plans it will show what youâre getting for whatâs being paid. Also note that as new things are added at particular levels, on the paid plans they will become available to you when ready and available. This is based on update channel and plan chosen.
With Proxmox your paying per cpu socket, potentially including per host and this is per year. However with Vates VMS on the most basic plans, per year and on higher ones per host per year. No having to deal with costs, per cpu socket or core with Vates. Thus more predictable costs, thus making it much cheaper for you in the long run!!
So if you have an infrastructure of no more than 3 hosts max depending on requirements, then either Essentials or Essentials+. However more than 3 hosts requires you to go for either Pro or Enterprise plans. Note that Enterprise plan requires a minimum of 4 hosts!
-
@john.c said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c correct. It's the auto updates and automations that come with the appliance that I am after. I believe the trial is only one month? Or possibly only 15 days? The support element is mostly irrelevant to me/us. I do a fair bit of automation via Ansible/Terraform, so developing our own unique library of Templates is ideal. Again, new to all this. So, it may just be that I've not come across this within my XO from "sources" build.
To your point - I was referring to XO Community = to XO Sources.
We may be unique in our internal policies to test for min 9-12 months prior to subscription? Proxmox licensing worked very well for us, because even when our three node HA edge cluster was in production, we were still able to license per the lowest tier which mad the whole stack so much more financially viable. I think we have 2/3 nodes on basic licensing and 1 may even be on Community! We are very technically savvy bunch that has managed to get by on this thus far.
Thanks for the comments/feedback. Much appreciated!
@cichy Though do note that you can make your case to Vates staff, during the trial if you find you donât have enough time to test. Just donât string them along by gaming the trial offer, to the point it becomes of infinite length, in a similar fashion to another organisation which wonât be named.
Also Netdata is a valuable plugin available in the appliance version of Xen Orchestra (XOA). A useful part of any monitoring solution.
The updating functionality in Xen Orchestra has recently gained the capability to be scheduled to run regularly. Finally in the last couple of months, Vates has completely re-done the backup feature in Xen Orchestra. If your workplace operates in regulated industry or policies are for air gapped infrastructure then Vates have most definitely got you covered with Pro and Enterprise plans!!
The XO Hub feature is only available to the appliance version as it is tied, to the Vates IT infrastructure. As well as likely the user account. Another feature present in the appliance version is the capacity for your Xen Orchestra settings, to be synchronised against the Vates account!
You may be very technically minded and/or your team, but as you state your new to the Vates VMS stack. Your access to their paid support, through the subscription support plan will pay for itself. Additionally your supporting (funding) future work on the software Vates releases. They can help you track down issues, as developers and thus root out what causes problems. Plus as members of the Xen Project and through that Linux Foundation, this will likely prove valuable - influence on future development.
If you pay yearly and sufficient multiple years, youâll have the following based on choice made:-
- 1 Year - No Savings
- 3 Years - Up to 10% Savings in 3 years
- 5 Years - Up to 15% Savings in 5 years
Check the comparison between the plans it will show what youâre getting for whatâs being paid. Also note that as new things are added at particular levels, on the paid plans they will become available to you when ready and available. This is based on update channel and plan chosen.
With Proxmox your paying per cpu socket, potentially including per host and this is per year. However with Vates VMS on the most basic plans, per year and on higher ones per host per year. No having to deal with costs, per cpu socket or core with Vates. Thus more predictable costs, thus making it much cheaper for you in the long run!!
So if you have an infrastructure of no more than 3 hosts max depending on requirements, then either Essentials or Essentials+. However more than 3 hosts requires you to go for either Pro or Enterprise plans. Note that Enterprise plan requires a minimum of 4 hosts!
This is all incredibly helpful. Thank you!
I will keep testing and then reach out to Vates once I have assessed the qty of servers Iâll be migrating to the new infra.
One question: were you referring to âNetboxâ integration? Currently using this to keep track of everything from rack (multiple) to power to server builds (GPU, drives, ram, cpu, etc). If that can be fully automated, it may be worth the cost alone!
-
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c correct. It's the auto updates and automations that come with the appliance that I am after. I believe the trial is only one month? Or possibly only 15 days? The support element is mostly irrelevant to me/us. I do a fair bit of automation via Ansible/Terraform, so developing our own unique library of Templates is ideal. Again, new to all this. So, it may just be that I've not come across this within my XO from "sources" build.
To your point - I was referring to XO Community = to XO Sources.
We may be unique in our internal policies to test for min 9-12 months prior to subscription? Proxmox licensing worked very well for us, because even when our three node HA edge cluster was in production, we were still able to license per the lowest tier which mad the whole stack so much more financially viable. I think we have 2/3 nodes on basic licensing and 1 may even be on Community! We are very technically savvy bunch that has managed to get by on this thus far.
Thanks for the comments/feedback. Much appreciated!
@cichy Though do note that you can make your case to Vates staff, during the trial if you find you donât have enough time to test. Just donât string them along by gaming the trial offer, to the point it becomes of infinite length, in a similar fashion to another organisation which wonât be named.
Also Netdata is a valuable plugin available in the appliance version of Xen Orchestra (XOA). A useful part of any monitoring solution.
The updating functionality in Xen Orchestra has recently gained the capability to be scheduled to run regularly. Finally in the last couple of months, Vates has completely re-done the backup feature in Xen Orchestra. If your workplace operates in regulated industry or policies are for air gapped infrastructure then Vates have most definitely got you covered with Pro and Enterprise plans!!
The XO Hub feature is only available to the appliance version as it is tied, to the Vates IT infrastructure. As well as likely the user account. Another feature present in the appliance version is the capacity for your Xen Orchestra settings, to be synchronised against the Vates account!
You may be very technically minded and/or your team, but as you state your new to the Vates VMS stack. Your access to their paid support, through the subscription support plan will pay for itself. Additionally your supporting (funding) future work on the software Vates releases. They can help you track down issues, as developers and thus root out what causes problems. Plus as members of the Xen Project and through that Linux Foundation, this will likely prove valuable - influence on future development.
If you pay yearly and sufficient multiple years, youâll have the following based on choice made:-
- 1 Year - No Savings
- 3 Years - Up to 10% Savings in 3 years
- 5 Years - Up to 15% Savings in 5 years
Check the comparison between the plans it will show what youâre getting for whatâs being paid. Also note that as new things are added at particular levels, on the paid plans they will become available to you when ready and available. This is based on update channel and plan chosen.
With Proxmox your paying per cpu socket, potentially including per host and this is per year. However with Vates VMS on the most basic plans, per year and on higher ones per host per year. No having to deal with costs, per cpu socket or core with Vates. Thus more predictable costs, thus making it much cheaper for you in the long run!!
So if you have an infrastructure of no more than 3 hosts max depending on requirements, then either Essentials or Essentials+. However more than 3 hosts requires you to go for either Pro or Enterprise plans. Note that Enterprise plan requires a minimum of 4 hosts!
This is all incredibly helpful. Thank you!
I will keep testing and then reach out to Vates once I have assessed the qty of servers Iâll be migrating to the new infra.
One question: were you referring to âNetboxâ integration? Currently using this to keep track of everything from rack (multiple) to power to server builds (GPU, drives, ram, cpu, etc). If that can be fully automated, it may be worth the cost alone!
@cichy Yes can be fully automated with Netbox, when coupled with Snipe-IT software, or the new extra modules for Netbox.
Checkout OpenTofu and OpenBAO both will be valuable and useful. OpenTofu is a fork of HashiCorp Terraform. Thereâs an official Vates module for OpenTofu. While OpenBao is a fork of HashiCorp Vault.
Thereâs a in preview module to allow PowerShell scripting remote management, on Windows or other workstations with it installed.
-
said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c correct. It's the auto updates and automations that come with the appliance that I am after. I believe the trial is only one month? Or possibly only 15 days? The support element is mostly irrelevant to me/us. I do a fair bit of automation via Ansible/Terraform, so developing our own unique library of Templates is ideal. Again, new to all this. So, it may just be that I've not come across this within my XO from "sources" build.
To your point - I was referring to XO Community = to XO Sources.
We may be unique in our internal policies to test for min 9-12 months prior to subscription? Proxmox licensing worked very well for us, because even when our three node HA edge cluster was in production, we were still able to license per the lowest tier which mad the whole stack so much more financially viable. I think we have 2/3 nodes on basic licensing and 1 may even be on Community! We are very technically savvy bunch that has managed to get by on this thus far.
Thanks for the comments/feedback. Much appreciated!
@cichy Though do note that you can make your case to Vates staff, during the trial if you find you donât have enough time to test. Just donât string them along by gaming the trial offer, to the point it becomes of infinite length, in a similar fashion to another organisation which wonât be named.
Also Netdata is a valuable plugin available in the appliance version of Xen Orchestra (XOA). A useful part of any monitoring solution.
The updating functionality in Xen Orchestra has recently gained the capability to be scheduled to run regularly. Finally in the last couple of months, Vates has completely re-done the backup feature in Xen Orchestra. If your workplace operates in regulated industry or policies are for air gapped infrastructure then Vates have most definitely got you covered with Pro and Enterprise plans!!
The XO Hub feature is only available to the appliance version as it is tied, to the Vates IT infrastructure. As well as likely the user account. Another feature present in the appliance version is the capacity for your Xen Orchestra settings, to be synchronised against the Vates account!
You may be very technically minded and/or your team, but as you state your new to the Vates VMS stack. Your access to their paid support, through the subscription support plan will pay for itself. Additionally your supporting (funding) future work on the software Vates releases. They can help you track down issues, as developers and thus root out what causes problems. Plus as members of the Xen Project and through that Linux Foundation, this will likely prove valuable - influence on future development.
If you pay yearly and sufficient multiple years, youâll have the following based on choice made:-
- 1 Year - No Savings
- 3 Years - Up to 10% Savings in 3 years
- 5 Years - Up to 15% Savings in 5 years
Check the comparison between the plans it will show what youâre getting for whatâs being paid. Also note that as new things are added at particular levels, on the paid plans they will become available to you when ready and available. This is based on update channel and plan chosen.
With Proxmox your paying per cpu socket, potentially including per host and this is per year. However with Vates VMS on the most basic plans, per year and on higher ones per host per year. No having to deal with costs, per cpu socket or core with Vates. Thus more predictable costs, thus making it much cheaper for you in the long run!!
So if you have an infrastructure of no more than 3 hosts max depending on requirements, then either Essentials or Essentials+. However more than 3 hosts requires you to go for either Pro or Enterprise plans. Note that Enterprise plan requires a minimum of 4 hosts!
This is all incredibly helpful. Thank you!
I will keep testing and then reach out to Vates once I have assessed the qty of servers Iâll be migrating to the new infra.
One question: were you referring to âNetboxâ integration? Currently using this to keep track of everything from rack (multiple) to power to server builds (GPU, drives, ram, cpu, etc). If that can be fully automated, it may be worth the cost alone!
Yes can be fully automated with Netbox, when coupled with Snipe-IT software, or the new extra modules for Netbox.
Checkout OpenTofu and OpenBAO both will be valuable and useful. OpenTofu is a fork of HashiCorp Terraform. Thereâs an official Vates module for OpenTofu. While OpenBao is a fork of HashiCorp Vault.
Thereâs a in preview module to allow PowerShell scripting remote management, on Windows or other workstations with it installed.
@cichy Depending on the size of infrastructure etc. Were you making use of the power efficiency feature in VMware? If so make sure you let them know, as will help to set priorities of any relevant features in the back log.
Thereâs a REST API available and in active development for XOA. Also has web hooks support to aid automation. Make sure you check out Vates blogs on XO6 development and recent AI blog posts. Given what you do, would be very much of interest!
In the matter of NetBox avoid using Essentials (non plus) plan then, it only is available from Essentials+ upwards, when on XOA (appliance). With XO:CE itâs available from the start.
The NetBox integration works by syncing tags set on Xen Orchestra, as well as other things which are covered by the integration. You can get Snipe-IT plugins for NetBox and vice versa, alternatively you can use Netbox Labâs Discovery add-on NetBox module with it. Will discover and document everything on the infrastructure!!
Xen Orchestra NetBox integration handled the Vates VMS related parts (including VMs and XCP-ng Hosts).
-
@cichy Additionally you can use XO Proxy, for multi-site instances of Vates VMS (https://vates.tech/xen-orchestra-proxy/). Plus the items for Terraform etc are in the DevOps add-on (https://vates.tech/devops-tools).
Given your multiple offices around the world youâll likely have, multiple servers and/or hosts at each location. So XO Proxy or site VPN links will be a must.
XO Proxy would for the Xen Orchestra related activities be most useful. It will make handling operations like backup, much easier with the proxies performing actions on the remote sites. Less load on the central Xen Orchestra instance!
-
@john.c thanks again for all this info!
I plan to meet up with the team this week to assess our objectives and KPI's; in the meantime, all of the above has helped tremendously. I'm currently messing around with establishing K8S + Swarm clusters, testing the automation capabilities, XCP-ng is proving to be quite flexible. Learning the nuances of dynamic resource allocation (CPU/RAM, etc.), there are some nuanced differences from vSphere/Proxmox.
Again, thanks very much for your help. I've made note of all your comments above. Especially references to Terraform/Vault alternatives! These are gold.
-
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c thanks again for all this info!
I plan to meet up with the team this week to assess our objectives and KPI's; in the meantime, all of the above has helped tremendously. I'm currently messing around with establishing K8S + Swarm clusters, testing the automation capabilities, XCP-ng is proving to be quite flexible. Learning the nuances of dynamic resource allocation (CPU/RAM, etc.), there are some nuanced differences from vSphere/Proxmox.
Again, thanks very much for your help. I've made note of all your comments above. Especially references to Terraform/Vault alternatives! These are gold.
@cichy Also thereâs a SR maintenance mode available, something useful for when work needs to be done, on bare metal shared storage.
By the way when your personal notebook blog is fully operational, I would love to subscribe to receive notifications of updates. As we weâll likely be able to learn from each other.
Was on Saturday 9th August 2025 following the release of Debian 13.0.0 (code name âTrixieâ).
-
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c correct. It's the auto updates and automations that come with the appliance that I am after. I believe the trial is only one month? Or possibly only 15 days? The support element is mostly irrelevant to me/us. I do a fair bit of automation via Ansible/Terraform, so developing our own unique library of Templates is ideal. Again, new to all this. So, it may just be that I've not come across this within my XO from "sources" build
Take a look at my provide or lookup Jarli01 on GitHub if you want a simple yet effective installation and maintenance approach to installing and managing XOCE.
-
@DustinB said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c correct. It's the auto updates and automations that come with the appliance that I am after. I believe the trial is only one month? Or possibly only 15 days? The support element is mostly irrelevant to me/us. I do a fair bit of automation via Ansible/Terraform, so developing our own unique library of Templates is ideal. Again, new to all this. So, it may just be that I've not come across this within my XO from "sources" build
Take a look at my provide or lookup Jarli01 on GitHub if you want a simple yet effective installation and maintenance approach to installing and managing XOCE.
@DustinB They mentioned needing the updates and related automations. Also given the size of the organisation that they are working for, theyâll likely need the QA of XOA in production.
If you check out Hok+ (https://www.hok.com/) website then scroll down, to the bottom they list all of their offices around the world. Also you can get statistics about the numbers of employees.
@cichy Am I correct about the above please?
-
@john.c point being? Nothing prevents this person from getting XOA once they are live, but staging and testing XOCE has been completely stable.
-
@cichy How things go with this switch from VMware, to Proxmox now to Vates VMS. Can potentially impact the software part of the architectural solutions, Hok+ provides your clients. Especially when implementing AI!
-
@john.c So hypothetical issues that may require paid support for a testbed is your concern. Is that correct?
-
@DustinB said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c So hypothetical issues that may require paid support for a testbed is your concern. Is that correct?
XOCE is alright for test bed, but outside of this in a production environment the use of XOA appliance is likely required.
-
@john.c said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@DustinB said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c correct. It's the auto updates and automations that come with the appliance that I am after. I believe the trial is only one month? Or possibly only 15 days? The support element is mostly irrelevant to me/us. I do a fair bit of automation via Ansible/Terraform, so developing our own unique library of Templates is ideal. Again, new to all this. So, it may just be that I've not come across this within my XO from "sources" build
Take a look at my provide or lookup Jarli01 on GitHub if you want a simple yet effective installation and maintenance approach to installing and managing XOCE.
@DustinB They mentioned needing the updates and related automations. Also given the size of the organisation that they are working for, theyâll likely need the QA of XOA in production.
If you check out Hok+ (https://www.hok.com/) website then scroll down, to the bottom they list all of their offices around the world. Also you can get statistics about the numbers of employees.
@cichy Am I correct about the above please?
This is correct. @DustinB ~ I am using this XO sources script to install/update/maintain XO atm. Though, I am on a Mac (ARM) which means I am unable to install XO to manage pools/hosts locally.
I'm going to push the CE/Sources ver as far as I can. It has been noted (by @john.c ) that two incredibly useful 'plugins' - net data/netbox - are not available on the XO Sources edition.
Once again, I appreciate the feedback and comments - all very helpful.
-
@cichy You can absolutely install netdata on your hosts https://xcp-ng.org/forum/topic/2288/netdata-package-is-now-available-in-xcp-ng, you simply don't get a SPOG from within XO unless you're on XOA.
It certainly appears that netbox can be configured as well on XOCE as well
This install is using my script, I can't speak for ronivoy's but the plugin is definitely there.
