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).
@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.
Terraform provider release: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.36.0
Pulumi provider release: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.3.0
I created a GitHub issue to track this feature request: https://github.com/vatesfr/terraform-provider-xenorchestra/issues/378
Whoo this looks very nice! Thank you for sharing this tool with us!
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
This is the pre-release version, which includes the changes to the memory_max field and adds the new memory_min field.
https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.2.0-alpha.1
@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.
Hi, thank you for the example! We will take a look. It could be a good idea to have a dedicated documentation/web page with usage examples of 'DevOps' tools 
@deefdragon can you check if /sys/hypervisor/uuid matches your VMs UUID?
Hi,
Do you know what causes the system UUID to change and not match the VM UUID?
In the tests I have run (with Debian and Microk8s), it never changed.
@deefdragon We are still trying to figure out why the DHCP isn't working. Our tests showed no issues with the recipe and DHCP.
We don't yet plan to enable up/down scaling for the recipe, but we are working on adding the CCM. We welcome suggestions: what do you need and how would you like the up/down scaling feature to work in the XOA recipe?
@deefdragon Can you try with static IPs?
Does your network have Internet access? The recipe needs it to update Debian and install microk8s.
Hi @deefdragon ,
Can you share the settings you used in the form?
According to the logs you have an issue with the network: can you check that the dhcp is working well (attributed IP address, netmask, gateway, etc. you can see in the console/screenshot) ?
Maybe you can try to reboot the VM, and try to connect again in ssh. If it works, you can extract the cloud-init logs from /var/log/cloud-init-output.log.
Cyrille
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 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
