1. Home
  2. Xen Orchestra

Subcategories

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

    486 Topics
    4k Posts
    johnnezeroJ
    Affinity Manager Plugin WHAT: In keeping with my previous project (Tag-Automation Plugin, found here), I am releasing the Affinity Manager Plugin, which is a fully tag-driven plugin for Xen Orchestra. It is designed to provide VM placement and grouping controls based on assigned tags, which are managed by predefined tag rules. PROGRAM FEATURES Host Affinity (RunOn) Run VMs on specific host group (e.g. a particular data center or set of hosts) Host Anti-Affinity (NotOn) Keep VMs off of specific host group VM Keep-Together (KeepTogether) Keep named group of VMs on the same host (follows Leader VM) VM Separation (KeepApart) Spread named group of VMs across unique hosts (best-effort) VM TAG SYNTAX Apply tags to VMs in the XO UI: VM TAG / RULE EXAMPLE MEANING AM-RunOn_{HostGrpName} AM-RunOn_P1-DC2-HOST VM should run on hosts tagged P1-DC2-HOST AM-NotOn_{HostGrpName} AM-NotOn_P2-DC1-HOST VM should NOT run on hosts tagged P2-DC1-HOST AM-KeepTogether_{GrpName} AM-KeepTogether_AppStack1 Keep all group VMs on same host (follows Leader VM) AM-KeepApart_{GrpName} AM-KeepApart_DBCluster1 Spread group VMs across unique hosts (best effort) Note: Multiple rules can be combined on a single VM. For example, a VM can have both AM-RunOn_P1-DC1-HOST and AM-KeepTogether_WebCluster simultaneously. HOST TAG SYNTAX Apply tags to hosts in the XO UI (i.e. to define host groups): EXAMPLE HOST TAG POOL LOCATION P1-DC2-HOST POOL-1 Data Center 2 P2-DC1-HOST POOL-2 Data Center 1 INSTALLATION Note: "Airgap" in the tar.gz file below, simply means the bundle includes all required dependencies for both an offline or online installation. Download the latest airgap release tarball from GitHub: https://github.com/johnezero/xo-affinity-manager/releases SCP the tarball to your XOA: scp xo-affinity-manager-airgap-vX.X.X.tar.gz <xoa-user>@<xoa-ip>:/tmp/ Create the plugin folder: sudo mkdir -p /usr/local/lib/node_modules/xo-server-affinity-manager Extract directly into the plugin directory: sudo tar -xzvf /tmp/xo-affinity-manager-airgap-vX.X.X.tar.gz -C /usr/local/lib/node_modules/xo-server-affinity-manager/ --strip-components=1 Restart xo-server: sudo systemctl restart xo-server Verify registration: sudo journalctl -u xo-server -n 100 --no-pager | grep -A3 "affinity-manager" You should see: [INFO] xo-affinity-manager: Plugin factory called -- xo context: YES [INFO] xo-affinity-manager: Plugin loaded -- waiting for core started. xo:plugin INFO successfully register affinity-manager Enable and configure the plugin in XO: Settings -> Plugins -> affinity-manager -> Enable CONFIGURATION (XO > Settings > Plugins) Enforcement Schedule — Run every 15 minutes, hourly, or daily (configurable) Dry Run Mode — Logs all intended actions without migrating anything (default: ON) Log Path — Configurable path to the log (Created automatically if it does not exist). Pool Safety — Cross-pool migration is always blocked (i.e. Plugin only migrates VMs within the same pool) Log Rotatate — Rotate/compress log files at 10 MB (keeping 3 archives) LINKS GitHub: https://github.com/johnezero/xo-affinity-manager STANDARD DISCLAIMER HERE This software is provided AS-IS without any express or implied warranty. While this plugin is being used in a production environment managing live VMs, you should always review the code and test it in a non-production environment before full deployment. Note: The plugin is designed to ONLY take action on VMs with specific predefined tags assigned -- all other VMs are never touched. Use Dry-Run mode to preview all changes before applying them. That said, as always - your mileage may vary... [image: 1788399103619-johnezero-logo-small.png]

  • 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!

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

    529 Topics
    6k Posts
    P
    I've since reduced the number of NBD connections to 4. However, I'm actually still seing this happen. I thought it was resolved. But going back to confirm, proved I assumed wrong. I have therefore uploaded a new bugtools archive from the host server on the link @poddingue sent me earlier. I hope they can prove helpfull. If you'd like me to do anything else, then I'll happily help out. Cheers!

  • 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.

  • Terraform, Packer or any tool to do IaC

    51 Topics
    485 Posts
    CyrilleC
    @koushik you have to use the Helm controller addons for RKE2 to deploy autmatically the Helm chart for the Xen Orchestra CCM with the field spec.bootstrap set to true: Field | Default | Description -------------------------------------------------- `spec.bootstrap` | `false` | Set to True if this chart is needed to bootstrap the cluster (Cloud Controller Manager, etc) EDIT: I wrote a wiki page with what I've tested https://github.com/vatesfr/xenorchestra-cloud-controller-manager/wiki/Rancher-RKE2
Log in to post
Load new posts
  • K

    ISO won't show since XO6 Default

    5
    2
    0 Votes
    5 Posts
    857 Views
    MathieuRAM
    Hi @Kptainflintt, I don't think this is related to XO6, but probably to this PR: https://github.com/vatesfr/xen-orchestra/pull/9231 VDIs with snapshot_of: <something> are now recognized as snapshots
  • D

    XO 6 Official Release (for community)

    xo6 community life-cycle feedback
    4
    0 Votes
    4 Posts
    1k Views
    D
    I provided some feedback.
  • V

    Can't designate new master on XO source pool

    8
    0 Votes
    8 Posts
    1k Views
    V
    Tracked it down to it thinking there was a pool version mismatch... then when I tried to transition to a new master it would fail with Xmlrpc_client.Connection_reset ... digging deeper it was complaining that it couldn't restore from the wrong version. Lots of head banging later... I setup a backup for the pool metadata and forced the backup immediately. TADA... I can now change the master with no issues at all.
  • snk33S

    XOA gets disconnected very often

    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    Yes, there's a possible weird combo between XOSTOR and HA in some situations. Let me add @ronan-a or @dthenot in the loop. It's likely that XOA disconnection is just a visible symptom of something else. It's not ultra trivial to reproduce though.
  • W

    Staring up a shutdown VM in XO 6

    4
    0 Votes
    4 Posts
    876 Views
    W
    @olivierlambert Thank you. I thought maybe I was losing my mind/eye sight, especially after reading that google search indicating there was a start button in 6.
  • P

    2FA doesn't load graphics properly after XO6 went default (XO from source)

    Solved
    5
    1
    0 Votes
    5 Posts
    718 Views
    olivierlambertO
    Excellent news
  • P

    Failed unmounting remotes at XO/XOA shutdown

    4
    1
    0 Votes
    4 Posts
    911 Views
    P
    No idea if anyone have "fixed" anything No, the XO commit 5fcb6 hang for ~3 min at reboot today. edit: I disabled the sceduled reboot yesterday.
  • P

    XO5 breaks after defaulting to XO6 (from source)

    53
    1
    0 Votes
    53 Posts
    12k Views
    M
    @MathieuRA I disabled Traefik and reverted to my old XO config (port 443, ssl encryption, http to https redirection), rebuild the docker container using your branch and tested: it is working fine on my end now Thank you very much! I did not expect this to get fixed so fast!
  • K

    Plugins in XO6?

    6
    0 Votes
    6 Posts
    730 Views
    olivierlambertO
    It won't disappear tomorrow, but I'd like to phase it out sooner than later (before 2027? who knows)
  • A

    Xen Orchestra from source ignores config.toml from /etc/xo-server/

    2
    0 Votes
    2 Posts
    469 Views
    A
    Ok I've figured out root cause. My config override has only one option: ignoreVmSnapshotResources = true And I had to change it with adding [selfService] on a line below Also I found out that override config for XO5 interface needs to have absolute paths to xo-web and @XenOrchestra in it. With relative paths it didn't work.
  • M

    LUKS Secured VM via Cloud Config

    1
    0 Votes
    1 Posts
    243 Views
    No one has replied
  • ForzaF

    Retention for log files and audit logs

    6
    0 Votes
    6 Posts
    1k Views
    eveaneE
    I would like to suggest to configure a remote syslog server. it centralizes all the log s and give you full control over the retention. It would also avoid situation where a disk full would impact your logging as well XCP-ng or XOA host operations. For your XCP-NG host go to you POOl, select Advanced tab and configure the Remote syslog host section to point to your syslog server. For XOA, you can follow the instruction here : https://docs.xen-orchestra.com/backups#send-xo-logs-to-an-external-syslog-server
  • ditzy-oliveD

    This topic is deleted!

    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • idealI

    HOST_NOT_ENOUGH_FREE_MEMORY

    4
    0 Votes
    4 Posts
    679 Views
    P
    @ideal perhaps you could use advantage of dynamic memory https://docs.xcp-ng.org/vms/#dynamic-memory to oversubscribe memory and have all 4 VMs up at once... or reduce the allocated memory of your VMs, you seem to have a pretty big VM in terms of memory in comparison to the 2 others on your screenshot
  • D

    SAML Auth with Azure AD

    Solved
    37
    1 Votes
    37 Posts
    13k Views
    D
    @olivierlambert Just to add another weird case of this situation I tell you my SAML-auth-adventures. I have just migrated a week ago from XOCE to XOA paid support this week and all the process was fine except the auth with the saml plugin. The commit I had in XOCE was [XO 5d92f - Master 3f604]. I compiled it the first week of this november so it wasn't very outdated. We use the MSEntraID SAML authentication and it was working fine in XOCE since at least one year ago. Mi process was like this: First, I installed XOA and imported the configuration from my old XOCE. Everything was fine and all was imported succesfully (backups, users, acls, etc.), including my plugin configurations. Note that I reused the https server certificate/private key and used the same IP and the same DNS (beacuse I turned off my XOCE before starting XOA). Everything was working fine except the saml auth plugin. I had the same "Internal server error" problem. I looked at the xo-server logs and the error was "invalid document signature" so, as Olivier said, we changed the configuration in MSEntraID to set the "Sign SAML response and assertion" on. Once we changed the configuration I thought the plugin would work again, but surprisingly not. If I try again SAML validation i still got the "Internal server error". When i checked again the xo-server logs I saw ahother exception, this time with the error "SAML assertion audience mismatch" and a reference to the issuer configuration of the plugin. The exact error I got from xo-server logs using "journalctl -u xo-server -f -n 50" was: "xoa xo-server[2370]: Error: SAML assertion audience mismatch. Expected: <id-of-MSEntraID-xo-validation> Received: spn:<id-of-MSEntraID-xo-validation>"I didn't understand this, because the configuration was exactly the same as I had in XOCE. In fact, I turned off XOA and turned on again XOCE just to test the plugin. The result was that in XOCE the plugin worked well. After many tries and some time of impostor syndrome we found the solution: I don't know why, but in XOCE compiled at the beginning of november you have to configure the issuer field of the plugin with the <id-of-MSEntraID-xo-validation> (8digit-4digit-4digit-4digit-12digit). Instead, in XOA deployed also this november, you have to set the issuer field to you XOA URL: https://<xo.company.net>/ I hope this will help, because it was a pain in the neck for us this week. BTW: @olivierlambert this "Internal server error" coming from an uncatched exception in the plugin was not very descriptive. Even a generic try-catch block just to show in the web interface the error would help... P.D.: I'm from Spain, so I do my best with my english P.D. 2: Great job with all the Vates virtualization stack! You are the best! Dani
  • C

    XOCE - ISO upload is renamed after upload to ISO SR

    18
    1 Votes
    18 Posts
    3k Views
    mxM
    We'd recently got a relevant experience regarding this weird renaming to uuids. We had one orchestra managing one pool. ISOs were in an ISO SR, with an nfs4 serving it underneath. All fine till then. We added one second pool to the orchestra. Just a single host by itself. One of the very next days we discovered that all names in the ISO SR had been replaced by uuids. Removing/readding the sr to the new pool helped temporarily. Usual names appeared again. But after a few more days, again uuids. Where uuids were appearing, we could not select anything from the dropdown list in the console's cdrom. The list per pool was unpopulated. We tried separate the shares by offering the new pool an nfs4 share from the NAS, actually sharing the same source dir. It did mount but now there was a uuid uniq constraint that was violated, so we could not see no files at all in this new SR. It would not be an illogical thought to have an 'iso sr' attached once to the orchestra and be offered by the orchestra to all managed pools, without uuids, without uniqs etc. There seems to be an unnecessary complication here I think.
  • ForzaF

    Set default resolution for UEFI

    5
    0 Votes
    5 Posts
    2k Views
    G
    I haven't had too much difficulty hitting the esc key in time to get into the EFI config. Click the start VM button, quickly click away from the display area and click in the display area, then toggle the esc key until I see it take effect. I know I have a couple running at 1920x1080, but that's actually kind of a pain. I only did that to try and get a larger RDP window, RDP may be limited by the original "monitor" resolution, but this might also be fixed in later updates. This one VM has been up for a few years. (edit, yes this has been changed, VMs with a 4x3 monitor now RDP is whatever I have set).
  • P

    License not working

    7
    0 Votes
    7 Posts
    911 Views
    DanpD
    Hi, I just responded to your ticket with the steps to update XOA to match your new license. Regards, Dan
  • S

    Is v6 preview not available on XO from source?

    Solved
    26
    2 Votes
    26 Posts
    14k Views
    acebmxerA
    @WorkAccount1000 Prior to myself finding that option in the config file use to run this command that worked as well.. cd /opt/xo/xo-web sudo yarn run turbo run build --filter @xen-orchestra/web
  • A

    Cannot migrate a vmdisk

    3
    0 Votes
    3 Posts
    648 Views
    A
    @bogikornel said in Cannot migrate a vmdisk: @ashinobi Known issue ... https://xcp-ng.org/forum/topic/11538/failed-to-migrate-vdi-two-local-sr/5?_=1763186433370 Thank you so much for letting me know. I'll follow your post so I can update that if they need more info on what is happening.