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 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.
-
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
-
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) -
Terraform Provider v0.36.0 and Pulumi Provider v2.3.0
- Read and expose boot_firmware on template data-source by @sakaru in #381
- Fixes VM creation from multi-disks template:
- All existing disks in the template are used if they are declared in the plan.
- All unused disks in the template are deleted to avoid inconsistency between the 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).
- Order of existing disk matches the declaration order in the plan
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
-
Terraform provider release v0.36.1
Fix for VM creation from templates with >=3 disks
-
-
Prioritization of VM startup AND shutdown sequencing! PLEASE - in the GUI (XO). So - without code - I can finally shutdown my servers accessing DB's prior to shutting down the DB server vm's themselves thereby saving myself from table corruption.
-
@cichy said in DevOps Megathread: what you need and how we can help!:
Prioritization of VM startup AND shutdown sequencing! PLEASE - in the GUI (XO). So - without code - I can finally shutdown my servers accessing DB's prior to shutting down the DB server vm's themselves thereby saving myself from table corruption.
@cichy In the past it was recommended to do this with an vApp and script. However this means editing the script or configuration file (if one’s created for the script). Which doesn’t make it as easy as the method, used by VMware ESXi for configuring the order and enabling the capacity.
Xen Orchestra and/or XCP-ng could really do with an UI (and API) based method of setting up and managing the VM boot and shutdown order.
