Subcategories

• Management

  VMs, hosts, pools, networks and all other usual management tasks.
  482 Topics

  4k Posts

  P

  I don't know the probe path well enough to say where the time goes, so this is mostly questions back at you. Is it the IQN probe or the LUN probe that drags, and are we talking seconds or minutes? Our docs describe it as two steps, xe sr-probe type=lvmoiscsi device-config:target=<ip> to list the IQNs, then the same call plus device-config:targetIQN=<iqn> for the LUNs behind one ( https://docs.xcp-ng.org/storage/manage-srs#discover-what-the-storage-offers-probe ). Timing those by hand on the host would at least split XO's share from XAPI talking to your array. It'd also help to know the target type, roughly how many IQNs and LUNs it exposes, and whether multipath is on, because my guess (and it's really a wild one) is that a wide target is where an enumeration gets expensive. Might be worth a mention to @Team-Storage, who'd know what the probe does underneath.
• Advanced features

  ACLs, Self-service, Cloud-init, Load balancing...
  106 Topics

  868 Posts

  M

  @tmk Confirmed bug on our side; thanks for the report. The plugin declared its secret with a random default in the config schema. That expression runs when the module is imported, so every xo-server process computes a different one, and xo-server never writes back the values ajv fills in from schema defaults. So if you copied the secret out of the plugin form without saving the configuration, scraping worked until the next restart, and Prometheus started getting 401s. Fix is here: https://github.com/vatesfr/xen-orchestra/pull/10290. The random default is gone. The secret is generated once on the first load and saved through the plugin configuration, so it survives a restart. If you already have one saved, it's left alone. Once it's merged it'll be on master for people building from sources, and it'll reach XOA in the next release.
• Backup

  All XO backup features: full and incremental, replication, mirrors...
  526 Topics

  6k Posts

  P

  Thanks for the feedback so far, folks!
• REST API

  Everything related to Xen Orchestra's REST API
  87 Topics

  650 Posts

  A

  @poddingue Borrow away - "smoke alarm" is a better name for it than anything we had, so we might borrow it right back. Since you mentioned reading the matrix - here is the classification you would be reading, straight from the file: grep access: dadl/xen-orchestra.dadl | sort | uniq -c 49 access: admin 21 access: dangerous 122 access: read 75 access: write 122 of the 267 tools are plain read - that is the entire surface a review-capped agent gets. The other 145 exist in the same file, but for that agent they might as well not. The whole security taxonomy is greppable plaintext - which is rather the point of a declarative format. And if anything in the matrix looks wrong or missing, this thread is exactly the right place - real-world corrections are how it improves.
• Infrastructure as Code

  Terraform, Packer or any tool to do IaC
  51 Topics

  472 Posts

  J

  New releases! Terraform Provider Xen Orchestra v0.40.0 This new release allows users to import VMs directly from Xen Orchestra into Terraform without recreating it or modifying manually the Terraform state. There is still some drift when importing it, but nothing that changes the real state of VM and we are currently on it! https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.40.0 Golang SDK for Xen Orchestra v1.17.0 v2 The network service is now available from the v2 client! You can now create, get and delete your network directly from it! v1 & v2 The template value in VM struct params has been fixed, We can now get the template id directly from it. https://github.com/vatesfr/xenorchestra-go-sdk/releases/tag/v1.17.0