Offline
We are pleased to announce the development of a CSI driver for Xen Orchestra 
It is currently under active development, but it's already available for testing with static volume provisioning only (i.e. use an existing VDI with its UUID).
Hello everyone 
We publish a development version of a Xen Orchestra Cloud Controller Manager!
It support the controllers cloud-node and cloud-node-lifecycle and add labels to your Kubernetes nodes hosted on Xen Orchestra VMs.
apiVersion: v1
kind: Node
metadata:
labels:
# Type generated base on CPU and RAM
node.kubernetes.io/instance-type: 2VCPU-1GB
# Xen Orchestra Pool ID of the node VM Host
topology.kubernetes.io/region: 3679fe1a-d058-4055-b800-d30e1bd2af48
# Xen Orchestra ID of the node VM Host
topology.kubernetes.io/zone: 3d6764fe-dc88-42bf-9147-c87d54a73f21
# Additional labels based on Xen Orchestra data (beta)
topology.k8s.xenorchestra/host_id: 3d6764fe-dc88-42bf-9147-c87d54a73f21
topology.k8s.xenorchestra/pool_id: 3679fe1a-d058-4055-b800-d30e1bd2af48
vm.k8s.xenorchestra/name_label: cgn-microk8s-recipe---Control-Plane
...
name: worker-1
spec:
...
# providerID - magic string:
# xeorchestra://{Pool ID}/{VM ID}
providerID: xeorchestra://3679fe1a-d058-4055-b800-d30e1bd2af48/8f0d32f8-3ce5-487f-9793-431bab66c115
For now, we have only tested the provider with Microk8s.
We will test the CCM with other types of Kubernetes clusters and work on fixing known issues.
Also a modification of the XOA Hub recipe will come to include the CCM.
More label will be added (Pool Name, VM Name, etc.).
You can install and test the XO CCM, and provide feedback to help improve and speed up the release of the first stable version. This is greatly appreciated 
Hello there,
We release a new version Terraform provider with improvements of the VM disk lifecycle!
Now you can expand a VM disk with Terraform without data loss.
Read the release note: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.32.0
These two bugs have been fixed in the latest release
Whoo this looks very nice! Thank you for sharing this tool with us!
@carloum70 Disk migration isn't supported by the provider yet. What you can do it's only ignore the changes to the sr_id of a given disk.
For example for the first disk:
lifecycle {
ignore_changes = [
disk[0].sr_id
]
}
You can also manually do the migration in XO and then after edit your HCL to update the sr_id with the new ID. It should do the trick.
The release v0.35.0 improves the logging of both the Xen Orchestra golang SDK and the Terraform Provider.
Now it should be easier to read the log using TF_LOG_PROVIDER=DEBUG (see the provider documentation)
The new version fixes bugs when creating a VM from a template #361:
The release: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.35.1
This new version introduces a new field, 'memory_min', for the VM resource and makes a slight change to the 'memory_max' field, which now sets both the dynamic and static maximum memory limits and providing better control of VM memory.
Full Changelog: https://github.com/vatesfr/pulumi-xenorchestra/compare/v2.1.0...v2.2.0
This new version introduces a new field, memory_min, for the VM resource and makes a slight change to the memory_max field, which now sets both the dynamic and static maximum memory limits and providing better control of VM memory.
Pulumi Provider v2.2.0
Terraform Provider v0.33.0
Xen Orchestra Go SDK v1.4.0
@bufanda said in DevOps Megathread: what you need and how we can help!:
@sid I made that request a while ago, and tried to look into myself too, but the current API of XenOrchestra just doesn't support it, there are many pieces missing from what I could see. I hope with XenOrchestra 6 the API wil support it though.
That's the point. We started working on it, but it wasn't possible to implement the required functionality in the TF provider using the current JRPC API. We are working with the XO team to provide feedback to make it happen with the REST API. I hope the backup resource will be available with XO6
NB: If you want to take a look, there are branches on the GitHub repository. These are for both the provider and the Golang client.
Hi @afk!
We are working on a new version of the Xen Orchestra Terraform provider to improve VM memory control.
In this new version, the memory_max setting will now set the maximum limits for both the dynamic and static memory.
There is also an optional new setting called 'memory_min', which can be used to set the minimum limit for dynamic VM memory.
This version will also resolve the issue with template memory limits used during VM creation.
Can you test this pre-release version and provide us with some feedback? Or maybe just tell us if this new behaviour is more likely to meet your needs?
https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.33.0-alpha.1
I will try asap to do a pre-release version for the Pulumi provider.
This new version brings improvement on the VM disks lifecycle made on the Terraform Provider.
https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.1.0
We released a new version of the Pulumi Xen Orchestra provider.
You can fail more information about the release here : https://xcp-ng.org/forum/post/92858
This release aims to ensure that the provider is up to date with the latest version of the pulumi-terraform-bridge. This will make it easier to follow new Pulumi versions.
The underlying Terraform provider XenOrchestra is updated to version 0.31.1, which fixes:
destroy_cloud_config_vdi_after_boot setting was ignored when the VM wasn't running. #345As the major version number suggests, this release introduces changes that break compatibility with previous versions (mostly deprecated functions and resources that have been removed).
Find the release in the Pulumi registry: https://www.pulumi.com/registry/packages/xenorchestra/
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.0.0
The provider is now available on the Pulumi official Registry 
https://www.pulumi.com/registry/packages/xenorchestra/
We added example for Yaml in the documentation.
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2
Hello,
If you want to discuss the Pulumi Provider in detail, let discuss here: https://xcp-ng.org/forum/topic/10592/pulumi-xen-orchestra-news
Hello there, we released a new Pulumi Xen Orchestra provider !
It's worth noting that the work on this was started by some contributors from DESY, and that now we (Vates) commit to support and maintain it. This demonstrate the strength of joined work from both community and Vates on free and open source softwares 
So what is offered is to declare your infrastructure as code, in
(pick the one you prefer 
)
And to deploy, maintain, and update it.
https://github.com/vatesfr/pulumi-xenorchestra/
https://www.pulumi.com/registry/packages/xenorchestra/
This new version builds on the improvements to the Terraform Provider regarding the disk lifecycle of a VM (TF provider release).
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.1.0
This release aims to ensure that the provider is up to date with the latest version of the pulumi-terraform-bridge. This will make it easier to follow new Pulumi versions.
The underlying Terraform provider XenOrchestra is updated to version 0.31.1, which fixes:
As the major version number suggests, this release introduces changes that break compatibility with previous versions (mostly deprecated functions and resources that have been removed).
Find the release in the Pulumi registry: https://www.pulumi.com/registry/packages/xenorchestra/
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.0.0
The provider is now available on the Pulumi official Registry
https://www.pulumi.com/registry/packages/xenorchestra/
We added example for Yaml in the documentation.
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2
The Pulumi Xen Orchestra provider is now available with Dotnet SDK!
@vates/pulumi-xenorchestrapulumi-xenorchestragithub.com/vatesfr/pulumi-xenorchestra/sdkPulumi.XenorchestraThe Pulumi schema doesn't support u64 (or i64), so we convert to a float64, which should get us at least 2^52 bits of precision while minimizing the breaking change (int -> float) for our users.
🟡 inputs: "memoryMax" type changed from "integer" to "number"🟡 properties: "memoryMax" type changed from "integer" to "number"🟡 "xenorchestra:index/VmDisk:VmDisk": properties: "size" type changed from "integer" to "number"Replace pulumi.Int(...) with pulumi.Float64(...)
Other SDKs do not seem to be affected by the changes.
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.0
Upgrade the Pulumi SDK and others libraries to the latest version and provider Java sdk.
If you are using Pulumi Xen Orchestra, please share your experiences and needs with us
@wezke you are welcome. let us know if you find the explanation for the problem with the template