XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Cyrille
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 33
    • Groups 2

    Cyrille

    @Cyrille

    Vates 🪐 DevOps Team
    20
    Reputation
    15
    Profile views
    33
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    Cyrille Unfollow Follow
    DevOps Team Vates 🪐

    Best posts made by Cyrille

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

      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

      posted in Infrastructure as Code
      CyrilleC
      Cyrille
    • RE: DevOps Megathread: what you need and how we can help!

      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

      posted in Infrastructure as Code
      CyrilleC
      Cyrille
    • RE: How to deploy the new k8s on latest XOA 5.106?

      These two bugs have been fixed in the latest release 🙂

      posted in Advanced features
      CyrilleC
      Cyrille
    • RE: Powershell script for backup summary reports

      Whoo this looks very nice! Thank you for sharing this tool with us!

      posted in Backup
      CyrilleC
      Cyrille
    • 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
      CyrilleC
      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
      CyrilleC
      Cyrille
    • 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
      CyrilleC
      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
      CyrilleC
      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
      CyrilleC
      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
      CyrilleC
      Cyrille

    Latest posts made by Cyrille

    • RE: CPU topology (sockets/cores) for new VMs deployed via Terraform

      I created a GitHub issue to track this feature request: https://github.com/vatesfr/terraform-provider-xenorchestra/issues/378

      gCyrille created this issue in vatesfr/terraform-provider-xenorchestra

      open CPU topology (sockets/cores) for new VMs deployed via Terraform #378

      posted in Infrastructure as Code
      CyrilleC
      Cyrille
    • RE: Powershell script for backup summary reports

      Whoo this looks very nice! Thank you for sharing this tool with us!

      posted in Backup
      CyrilleC
      Cyrille
    • 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
      CyrilleC
      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
      CyrilleC
      Cyrille
    • 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
      CyrilleC
      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
      CyrilleC
      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
      CyrilleC
      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
      CyrilleC
      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
      CyrilleC
      Cyrille
    • RE: Packer / Pulumi examples for Ubuntu and Windows VMs

      Hi, thank you for the example! We will take a look. It could be a good idea to have a dedicated documentation/web page with usage examples of 'DevOps' tools 👍

      posted in Infrastructure as Code
      CyrilleC
      Cyrille