@pszelestey Hi, yes, we've pushed an initial commit and a few more here https://github.com/vatesfr/cluster-api-provider-vates/ it is moging every day. Ping us in Matrix/Discord devops if you want to chat live while trying

@lknite Hello, sorry if replying in this old thread looks odd... but I wanted to share that we are starting to work on supporting Cluster API.

We have an internal proof of concept:
/home/nathanael/Images/Captures d’écran/Capture d’écran du 2026-05-05 17-12-22.png

@ThasianXi Hello, thanks for the report. It looks like the pull image step fails. Can you test that the token generated from Github is working and allows to pull the image.

Maybe a simple test on a docker install could ease the verification:

docker login ghcr.io -u USERNAME -p TOKEN
docker pull ghcr.io/vatesfr/xenorchestra-csi:v0.0.1

Also note that only "Classic" persona access token are supported.

More doc here https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-with-a-personal-access-token-classic

@ThasianXi Nice, thanks For now no other question related to the CCM. But I would be very interesting if you have some feedback about the CSI Driver. We'll work on this in the coming weeks. https://github.com/vatesfr/xenorchestra-csi-driver

@ThasianXi Thank you very much for this detailed feedback! Did you deployed the CCM on a new cluster or an existing? My question is to know if you relied on the CCM to initialize the nodes.

@ferrao Hey thanks, yes you are welcome to send a PR to improve the docs. It is based on Docusaurus, it is in the docs directory in https://github.com/vatesfr/xen-orchestra/tree/master/docs. Then pages are in the 2nd level docs directory.

@Mathieu yes indeed, I worked on this with @pierrebrunet PR https://github.com/vatesfr/xen-orchestra/pull/9042
Do you have any logs in xo-server service?

pierrebrunet289 opened this pull request in vatesfr/xen-orchestra

closed chore: update packages #9042

Hello @tmk, I will consider your post as a perfect feature request for the XO Terraform provider. I think that we also want to add support for CPU core/socket config.

@m4rCsi Very nice, thanks for sharing the repo. We will defintely look carefully as we are also working on writing a XO CSI Driver. Ping @Cyrille

@john.c Why not, can you share what would be the first tools to support and your use cases? I assume that if you are working in VSCode you might be useing some infrastructure as code, like Terraform or Pulumi or Ansible, isn't? In these case do you also have some related MCP servers enabled?

Hey @deefdragon did the installation finished using static IP addresses?

Hello @msupport we published a step by step guide, read more in the announcement there https://xcp-ng.org/forum/post/94268

Hello
We published a new blog post about our Kubernetes recipe:
You'll find there

• A step by step guide to create a production ready Kubernetes cluster, on top of your servers, in minutes!
• Some architecture insights

https://xen-orchestra.com/blog/virtops-6-create-a-kubernetes-cluster-in-minutes/

Thanks to @Cyrille

Hello, a community member also built a PowerShell module, using the (good old) jsonRPC https://github.com/rcfmartin/PSXO

let me ask a colleague about the task GUID-taskID mapping.

Hello @IvanK !

Maybe you did not saw this in news, but we released a PowerShell module https://github.com/vatesfr/xo-powershell

You can install it with Install-Module -Name xo-powershell -AllowPrerelease and connect Connect-XoSession -HostName "https://your-xo-server" -Token "your-api-token" easily.

Tell me what do you think of it.

xo-powershell moves from alpha to beta

The XO-PowerShell module is published in the :microsoft: PowerShell Gallery as v1.0.0-beta

https://www.powershellgallery.com/packages/xo-powershell/1.0.0-beta

Grab it with one powershell command:

Install-Module -Name xo-powershell -AllowPrerelease

Doc here

Thanks to @dinhngtu @iButcat

@coolsport00 Some forum users posted about this I think, like here

@coolsport00 Hello, I think you can find some relevant infos about GPU support, here in the forum, and also in the doc https://docs.xcp-ng.org/compute/#-gpu-passthrough

@coolsport00 Hello, I don't know the VMware feature you're talking about.

I would use Packer https://github.com/vatesfr/packer-plugin-xenserver and Cloud Base init https://cloudbase-init.readthedocs.io/en/latest/intro.html to build a Windows VM template. The sysprep would be run at the end of the packer for example using the provisioner powershell or in the shutdown_command

NB: do not forget to deploy guest tools inside the template.

@dinhngtu might have also suggestions

Hello @tmnguyen

About the XOSTOR limit, I read the devs saying it is like this as of now.
About using Linstor created by and for XOSTOR with another apps, in your case a Talos Kubernetes cluster, I think it should work, but all the volumes not created by XOSTOR would be unmanaged neither by XOSTOR nor by XO. So imagine, one admin would check in XO that a XOSTOR SR is not used anymore in the XO web ui, and would remove it. But would not think that it was also used for PV/PVC Kubernetes. There is this kind of risk. And as of now we do not support this.

By the way, we are going to start this month to write a CSI driver for Kubernetes for Xen Orchestra. This means from within a Kubernetes cluster you will create PVs/PVCs that would be backed by VM disks, aka VDIs

Subscribe to this topic if you want to be notified for the updates on this https://xcp-ng.org/forum/topic/10301/devops-megathread-what-you-need-and-how-we-can-help