I created a GitHub issue to track this feature request: https://github.com/vatesfr/terraform-provider-xenorchestra/issues/378
Team - DevOps
Posts
-
RE: CPU topology (sockets/cores) for new VMs deployed via Terraform
-
RE: SAML Auth with Azure AD
@Mathieu yes indeed, I worked on this with @pierrebrunet PR https://github.com/vatesfr/xen-orchestra/pull/9042
Do you have any logs inxo-server
service? -
RE: CPU topology (sockets/cores) for new VMs deployed via Terraform
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.
-
RE: How to kubernetes on xcp-ng (csi?)
-
RE: Powershell script for backup summary reports
Whoo this looks very nice! Thank you for sharing this tool with us!
-
RE: DevOps Megathread: what you need and how we can help!
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) -
RE: DevOps Megathread: what you need and how we can help!
Terraform Provider - Release 0.35.1
The new version fixes bugs when creating a VM from a template #361:
- All existing disks in the template are used if they are declared in the TF plan.
- All unused disks in the template are deleted to avoid inconsistency between the TF plan and the actual state.
- It is no longer possible to resize existing template disks to a smaller size (fixes potential source of data loss).
The release: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.35.1