Subcategories

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

    472 Topics
    4k Posts
    johnnezeroJ
    UPDATE: Tag-Based-Automation Plugin WHAT: The xo-tag-automation plugn is a native xo-server plugin that enforces VM performance tiers, manages group permissions, and synchronizes VM metadata -- all driven by VM tags and NFS-hosted CSV files (see below for more details). FEATURES PERFORMANCE SYNC Automatically applies CPU weights and IO priorities (sched-pri) based on VM performance tier tags: 0-core -- CPU weight: 2048 IO priority: 7 1-high -- CPU weight: 1024 IO priority: 7 2-normal -- CPU weight: 512 IO priority: 5 3-low -- CPU weight: 256 IO priority: 2 All tier weights and IO priorities are fully configurable in the plugin UI. An optional pool-specific tag suffix (e.g. -1=POOL1, -2=POOL2, etc.) allows you to manage multiple pools from a single XO instance without tag collisions. PERMISSION SYNC VM tags ending in -Admin, -Operator, or -Viewer automatically trigger XO Group creation and ACL assignments. CSV PERMISSION MANAGEMENT FILES Two CSV files on your NFS share drive the workflow: current-vms.csv A live export of your entire VM inventory. Contains UUID, Name, CurrentTags, NewTags, CurrentNotes, and NewNotes columns. Edit the NewTags and NewNotes columns and run the plugin (e.g. push the [Test plugin] button) to apply changes in bulk. The CSV auto-refreshes after each run. A staleness warning fires if the CSV has not been updated within a configurable number of days. preload-vms.csv Pre-stage tag and notes configurations for VMs that do not exist yet -- before they are migrated or created. The moment a VM matching a preload entry appears in XO, the plugin applies (on next scheduled interval) its tags and notes automatically and removes the entry from the preload file. PERMISSION AUTOPILOT Designed for active migration and onboarding projects. Automatically applies permission settings on scheduled interval, based on preload-vms.csv contents. Note: Should be disabled when not actively involved in migration projects. DRY-RUN / EXPORT-CSV MODE When Dry-Run is ON (the default), the plugin previews all changes in the XO logs without applying any changes, and simultaneously exports a fresh copy of all VM metadata to current-vms.csv with blank NewTags and NewNotes columns ready to fill in. Turn Dry-Run OFF to apply changes for real. RUN NOW (e.g. The [Test plugin] button) Trigger a full enforcement cycle instantly from the XO plugin UI without waiting for the next scheduled run. NFS LOGGING All activity is written to structured log files on your NFS share: xo-tag-automation.log -- full run log (auto-rotates at 2MB) xo-tag-automation.log.1 -- previous log backup xo-tag-automation-summary.log -- run summary entries only daily-summary.log -- nightly VM count and new VM report Logs are also available via xo-cli API methods (see below). LEGACY MIGRATION If you have an existing vm_metadata.csv from an older version, the plugin automatically renames it to current-vms.csv on first run. No manual migration needed. SECURITY -- PLEASE READ CAREFULLY This plugin automates infrastructure changes. Security is not optional. Please take both of the following seriously before enabling Permission Sync or Autopilot. -- REST API SERVICE ACCOUNT -- The plugin uses the XO JSON-RPC API internally. Use a dedicated service account -- never your personal admin credentials. Recommended setup (generic -- adapt to your environment): Create a dedicated XO user account for the service (e.g. a non-admin account with only the minimal access permissions required) Generate a scoped API token via xo-cli: xo-cli --register xo-cli token.create Store the token securely -- treat it like a password! Refer to the official Vates REST API documentation for full token management guidance: https://xen-orchestra.com/docs/restapi.html -- NFS SHARE SECURITY -- The NFS share hosts your CSV files and logs. Anyone with write access to the share can modify VM tags and permissions. STRONGLY RECOMMENDED Run the NFS share from a dedicated VM -- not a general-purpose NFS server. Restrict NFS exports to the XOA IP address only: /srv/nfs/share<XOAIP>/32(rw,sync,no_subtree_check,no_root_squash) Do NOT expose the NFS share to the general network or to end-user access. Admins who need to edit CSV files can SCP them to/from the XOA: EXAMPLE: Download CSV from XOA to your workstation scp <xoa-user>@<xoa-ip>:/path/to/current-vms.csv ./ Upload edited CSV back to XOA scp ./current-vms.csv <xoa-user>@<xoa-ip>:/path/to/current-vms.csv Use firewall rules to enforce NFS access at the network level in addition to the exports configuration Failure to secure the NFS share is a serious security risk. UPGRADING FROM THE STANDALONE SCRIPT If you installed the old standalone set-performance.sh script, you can remove it before enabling the plugin as follows: Remove the script: sudo rm /usr/local/bin/set-performance.sh Remove the crontab entry: crontab -e (delete the line referencing set-performance.sh) Note: The plugin handles its own scheduling via the XO UI. No manual cron configuration is required. INSTALLATION Download the latest airgap release tarball from GitHub: https://github.com/johnezero/xo-tag-automation_plugin/releases SCP the tarball to your XOA: scp xo-tag-automation-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-tag-automation Extract directly into the plugin directory: sudo tar -xzvf /tmp/xo-tag-automation-airgap-vX.X.X.tar.gz -C /usr/local/lib/node_modules/xo-server-tag-automation/ --strip-components=1 Restart xo-server: sudo systemctl restart xo-server Verify registration: sudo journalctl -u xo-server -n 100 --no-pager | grep -A3 "tag-automation" You should see: [INFO] xo-tag-automation: Plugin factory called -- xo context: YES [INFO] xo-tag-automation: Plugin loaded -- waiting for core started. xo:plugin INFO successfully register tag-automation Enable and configure the plugin options in XO: Settings -> Plugins -> tag-automation -> Enable XO-CLI API METHODS The plugin exposes several API methods accessible via xo-cli: xo-cli xo-server-tag-automation.exportCsv Export current VM inventory to current-vms.csv xo-cli xo-server-tag-automation.downloadCsvApi Print CSV content to stdout xo-cli xo-server-tag-automation.uploadCsvApi content@./current-vms.csv Push an edited CSV back to the NFS share xo-cli xo-server-tag-automation.getLog lines=100 View the last N lines of the plugin log xo-cli xo-server-tag-automation.getDailySummary View the nightly VM count summary xo-cli xo-server-tag-automation.getFilePaths Show all configured file paths LINKS GitHub: https://github.com/johnezero/xo-tag-automation_plugin Vates REST API docs: https://xen-orchestra.com/docs/restapi.html 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 tags assigned (e.g. untagged VMs are never modified). Use Dry-Run mode to preview all changes (via log file output) before applying them. That said, as always - your mileage may vary... [image: 1780884996846-johnezero-logo.jpg]
  • ACLs, Self-service, Cloud-init, Load balancing...

    104 Topics
    863 Posts
    laszlobortelL
    @florent Thanks for your reply! We have started to migrate thousands of VMs, so disk transfer speed is important for us.. We will also do our detailed tests soon with different threads setting and publish it here. I think threads=1 is a good and logical default, but not efficient. Others might complain if you set it to a higher value. Configuration option would be a real good solution.
  • All XO backup features: full and incremental, replication, mirrors...

    509 Topics
    5k Posts
    A
    @florent Ubuntu LVM file restore is working! (commit 38931) Now for another important issue I noticed with file restore (not directly LVM). Symbolic links don't show up. They should be restorable alone, but more importantly you need to be able to see and follow them for directories. For example. In Ubuntu, /bin is a link to /usr/bin. It is important to be able to click on /bin as a link to /usr/bin so files can be found in the backup. Another example is /vmlinuz that is a link to boot/vmlinuz-5.10.0-44-amd64. At worst the file restore should show a link (and it's destination), even if I can't restore the link. This is not just a LVM issue.
  • Everything related to Xen Orchestra's REST API

    85 Topics
    642 Posts
    1
    @poddingue Confirmed working, thank you so much for the heads-up, this made my day! Got it wired into the n8n flow and it's running perfectly. One gotcha for anyone else landing here, name_description gets rejected with a 422 "excess property", it has to be nameDescription. Working body: { "nameDescription": "nginx, app-1, app-2 | 2026-06-01" }
  • Terraform, Packer or any tool to do IaC

    50 Topics
    470 Posts
    CyrilleC
    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
  • Can I run multiple XOA

    7
    0 Votes
    7 Posts
    2k Views
    F
    THank you. Its up and running nothing broke
  • Turned off network boot for XOA in advanced and now broken

    Solved
    9
    0 Votes
    9 Posts
    2k Views
    olivierlambertO
    No problem, happy to help
  • Blank Screen CentOS 8 in fresh xcp-ng 8 installation

    14
    0 Votes
    14 Posts
    6k Views
    m076162M
    @MichaelCropper, to answer your question, yes, I enabled networking during the installation process. This allowed me to SSH in following the subsequent reboot to run yum groupinstall "Workstation". VGA was enabled for me and then Video RAM was at 16MiB. @ben20ben brings up good advice with the XCP-ng tools, install it and life gets easier.
  • Installed from sources - no plugins

    Solved
    10
    0 Votes
    10 Posts
    2k Views
    olivierlambertO
    Thanks for the feedback
  • suggestions for future upgrade...

    3
    0 Votes
    3 Posts
    677 Views
    cbaguzmanC
    @olivierlambert said in suggestions for future upgrade...: web hooks Thank @olivierlambert I'm going to read about web hooks in xoa.
  • Trusted headers - auth plugin

    6
    0 Votes
    6 Posts
    742 Views
    julien-fJ
    The idea is to give the best visibility to your plugin Though I don't think we'll ship it directly to our customer because it's an advanced use case
  • How do I remove "duplicate" host

    2
    0 Votes
    2 Posts
    507 Views
    T
    Nevermind. I don't know what I did, but eventually, the host was listed a halted and a Forget option was available. That did the trick.
  • xo-service not starting anymore after upgrade

    Solved
    9
    0 Votes
    9 Posts
    3k Views
    DanpD
    FWIW, this issue was likely due to using an outdated version of Node. The script is being updated to detect this scenario.
  • XO CE migrate fails for WinServer 2019 VM - "Internal Error"

    Solved
    11
    0 Votes
    11 Posts
    2k Views
    olivierlambertO
    Hard to tell. If it happens again, try immediately to compare XO behavior with other clients to see if we can tell where is the problem
  • Snapshot created and then deleted automaticly

    3
    2
    0 Votes
    3 Posts
    1k Views
    olivierlambertO
    This is probably a snapshot created to be able to coalesce by the system (when the VM is up). Try to shutdown the VM, I'm pretty sure it will coalesce without needing another snapshot.
  • Syntax and Examples for XO-Server webhooks

    9
    0 Votes
    9 Posts
    1k Views
    B
    Because I want to push users through a web portal interface which can obtain information from XO-Server for presentation back (ie: VM status, parameters, etc) whilst also allowing users to start/restart/shutdown VMs. We looked at XOA however it was too expensive and the free version has nag text messages which I don't want presented to users.
  • Copying Backups Offsite & Running on Cloud

    11
    1
    0 Votes
    11 Posts
    3k Views
    Marc.pezinM
    Hi, Thanks for picture update, I will fix it
  • Import VM from exported xva

    Solved
    3
    0 Votes
    3 Posts
    4k Views
    H
    Thank you again! This did the magic trick.
  • Delta and DR Backups Recommendations

    2
    1
    0 Votes
    2 Posts
    473 Views
    olivierlambertO
    They are two very different backup modes. Why not using delta + CR?
  • Static IP address with cloud-init

    2
    0 Votes
    2 Posts
    2k Views
    olivierlambertO
    Hi! Have you read https://xen-orchestra.com/docs/cloudinit.html#requirements ?
  • Installing other programs on XOA

    2
    0 Votes
    2 Posts
    422 Views
    olivierlambertO
    Hi, In any case, I strongly suggest that you open a support ticket first The answer might depend on what
  • XO Backup - Auto Start VM?

    Solved
    3
    0 Votes
    3 Posts
    670 Views
    D
    Sorry, you are right. The first time it didn't start and didn't show an error?? I just ran the job again with successful backup and it started without issue.
  • This topic is deleted!

    1
    1
    0 Votes
    1 Posts
    1 Views
    No one has replied
  • 0 Votes
    27 Posts
    19k Views
    olivierlambertO
    Short answer: no. Long answer: I'm not sure on the "how" we could do that. You should probably ask a XAPI developer about this. I'll try to get one or two here
  • Memory Usage wouldn't be displayed in XOA

    Solved
    8
    4
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    So yes, it was the service not started properly, so we didn't get the info into XOA You are welcome, enjoy it!