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.
-
@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.
-
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
-
@Cyrille Aah, I didn't know about the branches. I had started my own attempt to implement the feature, good to know I can abandon that work. Oh boy discovering the
settingsmap uses an empty key was a moment.OK, I will wait. Thanks to your team for the work on the terraform provider
-
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 thememory_maxfield, 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 -
@Cyrille Thanks for the release !
I just tested the happy path of settings (6GB min / 8GB max and 8/8) and it seems to work as expected.
Now, I can get rid of the workaround, that's awesome -
@olivierlambert Another useful item to aid in development processes and IaC operations. Is when using GitHub Copilot an MCP Server which will interface with the Vates VMS stack, so the agent can get context related to requests (queries). That way its responses can be properly grounded in the context of the stack, as well as the configuration, setup of the Vates VMS installation and its available resources.
Can the IaC team work on this, though may need other teams 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?
-
@nathanael-h said in 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?
@nathanael-h Pulumi for the infrastructure as code, with the code held on a private GitHub repository.
To aid in writing the IaC code as well as helping with provisioning VMs etc.
As well as during development of full stack website projects.
The appropriate servers are already enabled and configured, for GitHub Copilot use.
Visual Studio Code with GitHub Copilot.
-
@manilx I have proposed to the IaC team of Vates, a MCP Server for Vates VMS. Which can be used by GitHub Copilot or similar, if used when doing IaC etc.
