Subcategories

• Management

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

  4k Posts

  J

  @tjkreidl said: @john.c Wow, that was amazing -- not sure why my searches were unsuccessful, but many thanks! I think Github might be a good option for putting these on-line as a more reliable spot. And, yes, preserving images is always a challenge. I do hope some of that information may be useful to you and thanks much again for all your efforts, John! A bit of AI archeology combined with Internet Archive Wayback Machine helped. The AI helped to surface the exact URL of the blog posts and these were fed into Wayback Machine. Used the snapshot from 2022 anything newer and they weren’t there anymore. By the way it may be worth sending a donation Internet Archive’s way (if not done so already), as without this your blog posts would be truly gone for good!! Oh forgot to add GitHub and GitLab follows digital wills, so you can pass this off to another in a will, or generally be made read only while being kept up, when the time comes. So this hard work will be preserved even in the face of the end. Just please let me and the rest of us know where it’s at when done!
• Advanced features

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

  859 Posts

  J

  @gcpeters4 said: @john.c This is a good idea as well. If the previous suggestion of trying to do a DNS round robin approach doesn't work, this may be my best option. Thanks for taking the time to provide your suggestion! By the way my suggestion is recommended best practice from Microsoft for their Active Directory software and/or technology. My suggestion will be more likely to work if your DNS servers and requests have issues with Round Robin configuration. Plus with my solution you can easily add more servers as domain controllers to the cluster, as required and use replication to keep them consistent and up to date.
• Backup

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

  5k Posts

  A

  @Pilow said: @LoTus111 nice, but could be better you're missing the additionnal step in the TIPS section here : https://docs.xen-orchestra.com/xo5/troubleshooting#memory upgrading XOA to 8Gb is not enough, you have to tell xo services to be able to use this additionnal RAM. Question is if XO is built with 6gb initially does one still need to addjust memory via the command? Or only if expanding after the fact? Edit - to answer my own question and for others. After adding this function to my script it does appear the XO will setup appropriately with deployed with 6gb ram initially. ============================================== Xen Orchestra Memory Allocation ============================================== Setting Value ----------------------------- ----------------------------------- Total system RAM 5399 MB Current xo-server heap limit 4887 MB Recommended heap limit 4887 MB
• REST API

  Everything related to Xen Orchestra's REST API
  85 Topics

  633 Posts

  D

  @florent OK cool, thank you for the info.
• Infrastructure as Code

  Terraform, Packer or any tool to do IaC
  50 Topics

  470 Posts

  C

  Kubernetes CSI Driver for XO new release v0.3.0 Stable CSI Volume Identity: This decouples Kubernetes volume identity from backend storage lifecycle events (e.g. VDI migration between Storage Repositories) Topology-Aware Volume Provisioning: Dynamic provisioning now supports topology-aware pool selection. ️ Migration required from v0.2.0 to v0.3.0 Full release note: https://github.com/vatesfr/xenorchestra-csi-driver/releases/tag/v0.3.0