@deefdragon Can you try with static IPs?
Does your network have Internet access? The recipe needs it to update Debian and install microk8s.

Hi @deefdragon ,

Can you share the settings you used in the form?

According to the logs you have an issue with the network: can you check that the dhcp is working well (attributed IP address, netmask, gateway, etc. you can see in the console/screenshot) ?

Maybe you can try to reboot the VM, and try to connect again in ssh. If it works, you can extract the cloud-init logs from /var/log/cloud-init-output.log.

Cyrille

Release v2.1.0

This new version builds on the improvements to the Terraform Provider regarding the disk lifecycle of a VM (TF provider release).

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.1.0

Pulumi Xen Orchestra Provider - Release v2.1.0

This new version brings improvement on the VM disks lifecycle made on the Terraform Provider.

https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.1.0

Xen Orchestra Cloud Controller Manager in development

Hello everyone

We publish a development version of a Xen Orchestra Cloud Controller Manager!

It support the controllers cloud-node and cloud-node-lifecycle and add labels to your Kubernetes nodes hosted on Xen Orchestra VMs.

apiVersion: v1
kind: Node
metadata:
  labels:
    # Type generated base on CPU and RAM
    node.kubernetes.io/instance-type: 2VCPU-1GB
    # Xen Orchestra Pool ID of the node VM Host
    topology.kubernetes.io/region: 3679fe1a-d058-4055-b800-d30e1bd2af48
    # Xen Orchestra ID of the node VM Host
    topology.kubernetes.io/zone: 3d6764fe-dc88-42bf-9147-c87d54a73f21
    # Additional labels based on Xen Orchestra data (beta)
    topology.k8s.xenorchestra/host_id: 3d6764fe-dc88-42bf-9147-c87d54a73f21
    topology.k8s.xenorchestra/pool_id: 3679fe1a-d058-4055-b800-d30e1bd2af48
    vm.k8s.xenorchestra/name_label: cgn-microk8s-recipe---Control-Plane
    ...
  name: worker-1
spec:
  ...
  # providerID - magic string:
  #   xeorchestra://{Pool ID}/{VM ID}
  providerID: xeorchestra://3679fe1a-d058-4055-b800-d30e1bd2af48/8f0d32f8-3ce5-487f-9793-431bab66c115

For now, we have only tested the provider with Microk8s.

What's next?

We will test the CCM with other types of Kubernetes clusters and work on fixing known issues.
Also a modification of the XOA Hub recipe will come to include the CCM.
More label will be added (Pool Name, VM Name, etc.).

Feedback is welcome!

You can install and test the XO CCM, and provide feedback to help improve and speed up the release of the first stable version. This is greatly appreciated

The XO CCM repository
Installation doc

@john.c You can already use Yaml with the Xen Orchestra Pulumi provider

name: test-yaml
description: A minimal Pulumi YAML program
runtime: yaml
config: { 'pulumi:tags': { value: { 'pulumi:template': yaml } } }
variables:
  poolId:
    fn::invoke:
      function: xenorchestra:getXoaPool
      arguments:
        nameLabel: "Lab"
      return: id
  netId:
    fn::invoke:
      function: xenorchestra:getXoaNetwork
      arguments:
        nameLabel: "Lab"
        poolId: ${poolId}
      return: id
  localStorageId:
    fn::invoke:
      function: xenorchestra:getXoaStorageRepository
      arguments:
        nameLabel: "Local Storage"
      return: id
  templateId:
    fn::invoke:
      function: xenorchestra:getXoaTemplate
      arguments:
        nameLabel: "Debian 12 Cloud-init (Hub)"
        poolId: ${poolId}
      return: id
resources:
  vm:
    type: xenorchestra:Vm
    properties:
      nameLabel: "Pulumi yaml test"
      nameDescription: "test with pulumi yaml provider"
      cpus: 1
      memoryMax: 1073733632
      template: ${templateId}
      tags:
        - pulumi
      cloudConfig: |
        #cloud-config
        ssh_authorized_keys:
          - ***
      disks:
        - nameLabel: "OS"
          size: 8294967296
          srId: ${localStorageId}
      networks:
        - networkId: ${netId}
      powerState: "Running"

outputs:
  poolId: ${poolId}
  vmIp: ${vm.ipv4Addresses}

Tell us if it ins't working

Hello there,

We release a new version Terraform provider with improvements of the VM disk lifecycle!

Now you can expand a VM disk with Terraform without data loss.

Read the release note: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.32.0

Hi,
If you're familiar with Golang, I'm pretty sure the xenorchestra-go-sdk might be able to do what you want (except the network configuration within Windows, but for this you can use Ansible with Xen Orchestra Inventory plugin: read the blogpost.)

The Powershell module is quite new, and we are working on improving it. Please let us know what you are expecting from it

Pulumi Xen Orchestra Provider - Release v2.0.0

We released a new version of the Pulumi Xen Orchestra provider.

You can fail more information about the release here : https://xcp-ng.org/forum/post/92858

Release v2.0.0

This release aims to ensure that the provider is up to date with the latest version of the pulumi-terraform-bridge. This will make it easier to follow new Pulumi versions.

The underlying Terraform provider XenOrchestra is updated to version 0.31.1, which fixes:

• Issues with blocked operations when creating VMs. #344
• A problem where the destroy_cloud_config_vdi_after_boot setting was ignored when the VM wasn't running. #345

As the major version number suggests, this release introduces changes that break compatibility with previous versions (mostly deprecated functions and resources that have been removed).

Find the release in the Pulumi registry: https://www.pulumi.com/registry/packages/xenorchestra/

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.0.0

These two bugs have been fixed in the latest release

@ferrao Yes it is. At the end the task disappears unless there is an error / failure.

@ferrao open the VMs list (Home>VMs), click on "Filters" near the search bar, and then click "Save...", in the popup dialog enter a name for the filter and click "OK".

This should be enough to workaround the 2nd bug that happened at the end (that prevent to save the tag that is added to the clusters VMs)

@ferrao Thank you for the logs, with it I was able to reproduce the bug.

It's at the end of the recipe, when the tag associated with the k8s cluster is saved in the user's custom filters. This has no effect on the cluster creation, as this is done at the end when everything else is done.

To avoid this bug in future runs, you can save a custom filter from the search field in the VMs list.

About the first error you encounter, it's related to the template used to create the VM, which seems not available at the VM creation... I'm working on this to understand why.

@abreaux said in Kubernetes Recipe:

Is there any way to get the cloud-init used in the Hub Kubernetes recipe? Looking to customize the deployment using Terraform and I want to make sure I include all the same tasks.

What do you want to do actually? Do you want to "edit" a VM that has been deployed with the recipe (1), or do you want to deploy a new cluster that will copy the hub recipe (2)?

In case of (1), you can find the cloud-init content inside the VM itself: /var/lib/cloud/instance/cloud-config.txt

In the case of (2), the current version (5.105) of the k8s recipe is not really stable and is not intended to be used with Terraform. I can only recommend to find another solution (you can find some examples in the DevOps mega thread, like using Rancher).

In the next release of XOA, we have updated the Kubernetes recipe to use MicroK8s, which provides a light, open-source, scalable and production-ready Kubernetes distribution.

Release v1.5.2

The provider is now available on the Pulumi official Registry

https://www.pulumi.com/registry/packages/xenorchestra/

We added example for Yaml in the documentation.

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2

Hello,
If you want to discuss the Pulumi Provider in detail, let discuss here: https://xcp-ng.org/forum/topic/10592/pulumi-xen-orchestra-news

Hello there, we released a new Pulumi Xen Orchestra provider !

It's worth noting that the work on this was started by some contributors from DESY, and that now we (Vates) commit to support and maintain it. This demonstrate the strength of joined work from both community and Vates on free and open source softwares

So what is offered is to declare your infrastructure as code, in

• C# / .NET
• Go
• Javascript or Typescript
• Python
• Yaml

(pick the one you prefer )

And to deploy, maintain, and update it.

https://github.com/vatesfr/pulumi-xenorchestra/

https://www.pulumi.com/registry/packages/xenorchestra/

---

Release v2.1.0

This new version builds on the improvements to the Terraform Provider regarding the disk lifecycle of a VM (TF provider release).

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.1.0

Release v2.0.0

This release aims to ensure that the provider is up to date with the latest version of the pulumi-terraform-bridge. This will make it easier to follow new Pulumi versions.

The underlying Terraform provider XenOrchestra is updated to version 0.31.1, which fixes:

• Issues with blocked operations when creating VMs. #344
• A problem where the destroy_cloud_config_vdi_after_boot setting was ignored when the VM wasn't running. #345

As the major version number suggests, this release introduces changes that break compatibility with previous versions (mostly deprecated functions and resources that have been removed).

Find the release in the Pulumi registry: https://www.pulumi.com/registry/packages/xenorchestra/

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.0.0

---

Release v1.5.2

The provider is now available on the Pulumi official Registry

https://www.pulumi.com/registry/packages/xenorchestra/

We added example for Yaml in the documentation.

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2

---

Release v1.5.0

The Pulumi Xen Orchestra provider is now available with Dotnet SDK!

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

What's Changed

• Feat: Add dotnet support
• Add docs for Dotnet SDK and unify examples

The Pulumi schema doesn't support u64 (or i64), so we convert to a float64, which should get us at least 2^52 bits of precision while minimizing the breaking change (int -> float) for our users.

List of properties to be updated from "integer" to "number"/float64:

Resources

• "xenorchestra:index/vm:Vm":
  • 🟡 inputs: "memoryMax" type changed from "integer" to "number"
  • 🟡 properties: "memoryMax" type changed from "integer" to "number"

Types

• 🟡 "xenorchestra:index/VmDisk:VmDisk": properties: "size" type changed from "integer" to "number"

How to migrate Golang stack code

Replace pulumi.Int(...) with pulumi.Float64(...)

Other SDKs do not seem to be affected by the changes.

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.0

---

What's next?

Upgrade the Pulumi SDK and others libraries to the latest version and provider Java sdk.

If you are using Pulumi Xen Orchestra, please share your experiences and needs with us

@wezke you are welcome. let us know if you find the explanation for the problem with the template

@wezke Hi, I have no problem running your terraform plan, maybe there is a problem with the template you are using? How did you create it?

There is no warning during the tf execution?