docs: add doc for Xen Orchestra - XCP-ng #249
Conversation
| Define the version and architecture: | ||
|
|
||
| ```bash | ||
| export TALOS_VERSION=v1.11.5 |
There was a problem hiding this comment.
We have a variable to keep this updated automatically. Check https://github.com/siderolabs/docs/blob/main/public/snippets/custom-variables.mdx and how it's used in other guides.
There was a problem hiding this comment.
Nice 👍 I made the changes. Is good like this?
| | **Cloud-Init** | Enabled | To automatically pass the Talos configuration | | ||
| | **Advanced settings > Boot VM** | false | To not start the template VM after creation | | ||
|
|
||
| ### Via Xen Orchestra web UI |
There was a problem hiding this comment.
do you have a way to do this with CLI too? It would be great to have that as an optional tab because they tend to be more reliable for people trying it than UI
There was a problem hiding this comment.
We have a cli but "This CLI is mainly used as a debug tool, there's no 100% guarantee on its stability. Use it only if you really know what you do..."
I will check with it to have a working pipeline, otherwise I will try to write an alternative with the REST API.
|
|
||
| The [Terraform provider for Xen Orchestra](https://registry.terraform.io/providers/vatesfr/xenorchestra/latest) can be used as an alternative to the Xen Orchestra Web UI, enabling declarative and automated infrastructure management. An example is provided below: | ||
|
|
||
| ```hcl main.tf icon="file-heart" expandable |
There was a problem hiding this comment.
This code should go in our contrib repo and you can reference here. A README with the code over there will be more maintainable. https://github.com/siderolabs/contrib
|
This is a good start. I think my main question is how is this different than a single node XCP-ng? Do single nodes also use the orchestrate UI? I'm also curious if you have plans for an Omni infrastructure provider to make all these steps automatic for users. |
You can use the XOA UI from a single XCP-ng node up to multiple nodes on multiples pools. Otherwise, there is XO-Lite UI which is already installed on an XCP-ng node. However, the If needed, I can write a guide for an XO-Lite/Single XCP-ng node. However, at Vates, we strongly recommend using Xen Orchestra, as it makes many things easier, such as automatically mounting a Cloud-init disk with the configuration.
We are working on it, but it's still in the early stages. |
I wouldn't worry about a separate doc about XO-Lite but can you add a note that this guide doesn't work with XO-Lite? That's all I had available and didn't knew it was different from Xen Orchestra. |
…ered by that guide
It's true that the guide does not cover installation on an XCP-ng host without Xen Orchestra, so I removed the reference to XCP-ng. I added an 'Info' callout: This guide does not cover XCP-ng without Xen Orchestra installed, or XO Lite, even though some of the steps may be similar. |
2 participants
Hi,
I'm from Vates and I would like to provide some documentation to support the use of Talos on the Xen Orchestra platform.
Xen Orchestra supports cloud-init with an attached cloud-init disk. This can be used to configure Talos with an Nocloud platform image. This guide explains how to create a VM template that can be used to configure and boot a Talos VM in Xen Orchestra.
I mentioned XCP-ng because it is the virtualisation platform running behind, and this guide remains relevant for XCP-ng users, provided you adapt the steps originally written for the XO interface.