DevOps Megathread: what you need and how we can help!

[Cyrille]

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

[john.c]

@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?

[john.c]

@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.