Posts

• 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)

  posted in Infrastructure as Code

  C

  Cyrille
  
• 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

  posted in Infrastructure as Code

  C

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

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

  posted in Infrastructure as Code

  N

  nathanael-h
  
• RE: Pulumi Xen Orchestra - News

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

  What's Changed

  • feat: Update TF provider to get VM memory improvements by @gCyrille in https://github.com/vatesfr/pulumi-xenorchestra/pull/420

  Full Changelog: https://github.com/vatesfr/pulumi-xenorchestra/compare/v2.1.0...v2.2.0

  • JavaScript/TypeScript: @vates/pulumi-xenorchestra
  • Python: pulumi-xenorchestra
  • Go: github.com/vatesfr/pulumi-xenorchestra/sdk
  • .NET: Pulumi.Xenorchestra

  gCyrille opened this pull request in vatesfr/pulumi-xenorchestra

  closed feat: Update TF provider to get VM memory improvements #420

  posted in Infrastructure as Code

  C

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

  New releases for Terraform and Pulumi providers!

  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

  posted in Infrastructure as Code

  C

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

  Pulumi Xen Orchestra Provider - Pre-Release v2.2.0-alpha.1

  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

  posted in Infrastructure as Code

  C

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

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

  posted in Infrastructure as Code

  C

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

  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.

  posted in Infrastructure as Code

  C

  Cyrille