Subcategories

• Management

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

  4k Posts

  P

  Thanks for the numbers. So the whole chain drags: 4 to 5 minutes to list the ~90 LUNs, another 1 to 3 to validate one, and the create on top of that. From the XO side I can't tell where that time goes, XO itself, the host's storage layer, or the array answering slowly, and the one measurement that would split it is the host-side probe I mentioned: time xe sr-probe type=lvmoiscsi device-config:target=<ip>, then the same call with device-config:targetIQN=<iqn> added. If the CLI takes just as long, XO is mostly off the hook. A 90-LUN multipath target doesn't sound exotic to me, so probes taking minutes feel worth a proper look, though I honestly don't know what's normal at that scale. @Team-Storage, the numbers above are concrete now, in case it's worth a look on your side.
• Advanced features

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

  869 Posts

  T

  @mpiton Thanks for looking into this, I guess it wasn't apparent that I needed to click the Save Configuration button for that plugin. I did that and confirmed that the secret now survives an xo-server restart. Thanks again!
• Backup

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

  6k Posts

  P

  I think I may have found why, though someone on the XO side should check me on this. The filter builds its list from backup jobs that have at least one enabled schedule of their own, right? A sequence works the other way round: it gets its own timer and runs the member schedules from there. So once those member schedules are switched off, their jobs drop out of the filter and every VM they cover reads as not backed up. If that's right, it's a wrong answer rather than a missing feature, which matters because it changes who needs to look at it. I got there by reading the code with bad glasses, not by reproducing it on a real install, so treat that last step as my wild guess. Might be worth a mention to @Team-XO-Backend. Your dashboard idea could well be the better home for it anyway.
• 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