DevOps Megathread: what you need and how we can help!
-
Terraform provider release v0.37.0
- Enables the secure boot parameter for the VM resource
Terraform provider release: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.37.0
-
Hi here,
We have released documentation with our recommendations for those who want to run Talos in Xen Orchestra.
It is available in the official Sidero Labs documentation: Platform specific installation > Virtualized Platforms > Xen Orchestra
We are currently working on providing an example of a Talos cluster that has been created using Terraform.
Have fun
-
Congrats!
-
@Cyrille said in DevOps Megathread: what you need and how we can help!:
Hi here,
We have released documentation with our recommendations for those who want to run Talos in Xen Orchestra.
It is available in the official Sidero Labs documentation: Platform specific installation > Virtualized Platforms > Xen Orchestra
We are currently working on providing an example of a Talos cluster that has been created using Terraform.
Have fun
Nice ! Thank you for this.
Fwiw, I started to work on a PoC deployment of a talos cluster this summer and managed to do the full process with pulumi. I'll probably migrate to opentofu when I have everything setup as I want to clean things up.
The whole install and k8s bootstrap takes 2-3 minutes to deploy a 3 nodes control plane and 3 workers from start to finish. You even get the machine configs, kubeconfig and talosconfig as outputs. Then, I deployed fluxcd manually but you could even automate that in the deployment.
Overall, its really impressive and quite easy once you understand the way talos works. Highly recommended !
-
@afk Nice!
I haven't tried Pulumi yet. Does Talos have a provider for it?I'm working on improving the CCM to make it work with Talos. Especially the
cloud-node-label-synccontroller (as the cloud-controller is the Talos one) to get the XO topology in the node labels. -
@Cyrille said in DevOps Megathread: what you need and how we can help!:
@afk Nice!
I haven't tried Pulumi yet. Does Talos have a provider for it?I'm working on improving the CCM to make it work with Talos. Especially the
cloud-node-label-synccontroller (as the cloud-controller is the Talos one) to get the XO topology in the node labels.Yes there is a provider for it: https://www.pulumi.com/registry/packages/talos/
I guess its the auto-generated provider from the terraform one because I had some type checking errors in some places, but using python I could ignore that... I don't know if it has been fixed since.
I remember reading some terraform examples on blogs to write the pulumi config so converting one to the other should be straightforward. Unfortunately, I can't publish what I wrote because its quite messy but feel free to ask if you have some blockers.The CCM would be nice to have indeed ! Good luck on that.
-
XO CCM v0.2.0
This update make it working with Talos.
What's Changed
- Feat: record event when region zone changed
- Refactor: make xoClient and xoConfig available outside package scope (to be used by the CSI)
- Workaround for the SystemUUID sometimes in little-endian
https://github.com/vatesfr/xenorchestra-cloud-controller-manager/releases/tag/v0.2.0
Terraform Provider v0.37.2
What's Changed
- Fix xenorchestra_vdi data source: you can now filter VDI/ISO with the same name label using tags.
https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.37.2
-
Kubernetes CCM for Xen Orchestra v1.0.0-rc.1
We’re shipping v1.0.0-rc.1, our first release candidate on the road to a stable 1.0.0! This RC is feature-complete and ready for real-world use.
Please try it out and share any feedback—bugs, regressions, or usability notes—so we can polish the final release. Thank you for testing and helping us! 
https://github.com/vatesfr/xenorchestra-cloud-controller-manager/releases/tag/v1.0.0-rc.1
Golang SDK for Xen Orchestra v1.11.0
SDK v2:
- VM and Task services now match the latest REST API.
- Host service has been added for host data retrieval.
- Integration tests have also been strengthened to boost reliability.
The v2 SDK is gradually becoming our main library for all the other DevOps tools (Kubernetes drivers, Terraform provider…).
There are BREAKING CAHNGES in the v2 SDK, so please read the release notes carefully.
Remember that the v2 SDK is a beta version and can be subject to significant changes. The current semantic versioning we use is mostly for the v1 SDK. When the v2 SDK becomes stable, the major version number will increase.https://github.com/vatesfr/xenorchestra-go-sdk/releases/tag/v1.11.0
-
@nathanael-h As a further follow up the MCP agents include at minimum:-
- Pulumi
- MariaDB
Anyway I would really appreciate having an MCP Server which, can be used when writing IaC to provision and configure your customers’ systems. Can it be made available during this year please?
-
@vates-11940382 Hi All at Vates,
I just wanted to say a big thank you for the MCP support that’s now landing in Xen Orchestra. This is definitely a genuinely forward-thinking move, and it’s going to have a huge impact on how IaC tooling interacts with XCP-ng going forward.
MCP gives XO a clean, structured, read-only interface that modern AI-assisted tools (e.g Pulumi Neo, Copilot, Claude, Cursor, etc.) can understand natively. That’s a massive step toward making XCP-ng an AI-visible, AI-navigable platform - something no other virtualisation stack is doing yet.
What’s even more exciting is the long-term implication: this kind of openness and clarity is exactly what hyperscalers have been struggling with internally. If Vates continues down this path, it’s not unrealistic that MCP-native infrastructure could start attracting interest from much larger players - whether as customers, collaborators, or contributors.
The combination of:
- IaC
- MCP
- AI-assisted operations
- and XCP-ng’s open architecture
Puts Vates in a very strong position for the future.
Thanks again for pushing this forward. It’s a big deal, and it’s going to unlock a lot of possibilities for the community.
