IT Solutions Technology Blog

How to keep your XCP-ng system updated

[09:05 xcp-ng-01 ~]# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
* xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
* xcp-ng-updates: mirrors.xcp-ng.org
xcp-ng-base/signature | 473 B 00:00
xcp-ng-base/signature | 3.0 kB 00:00 !!!
xcp-ng-updates/signature | 473 B 00:00
xcp-ng-updates/signature | 3.0 kB 00:00 !!!
No packages marked for update
[09:05 xcp-ng-01 ~]#

How to find XCP-ng host-uuid because for many xe commands on XCP-ng you have to use a host-uuid=<…>

[09:23 xcp-ng-01 ~]# xe host-list
uuid ( RO) : e754cbb9-7bfd-4659-9f34-03bca65443f0
name-label ( RW): xcp-ng-01
name-description ( RW): Default install
[09:45 xcp-ng-01 ~]#

[09:55 xcp-ng-01 ~]# xe host-param-list uuid=e754cbb9-7bfd-4659-9f34-03bca65443f0 | grep version
API-version-major ( RO): 2
API-version-minor ( RO): 16
API-version-vendor ( RO): XenSource
API-version-vendor-implementation (MRO):
software-version (MRO): product_version: 8.2.1; product_version_text: 8.2; product_version_text_short: 8.2; platform_name: XCP; platform_version: 3.2.1; product_brand: XCP-ng; build_number: release/yangtze/master/58; hostname: localhost; date: 2023-10-18; dbv: 0.0.1; xapi: 1.20; xen: 4.13.5-9.38; linux: 4.19.0+1; xencenter_min: 2.16; xencenter_max: 2.16; network_backend: openvswitch; db_schema: 5.603
virtual-hardware-platform-versions (SRO): 0; 1; 2
[09:55 xcp-ng-01 ~]#

[10:08 xcp-ng-01 ~]# xenpm get-cpufreq-para | fgrep turbo
turbo mode : enabled
turbo mode : enabled
turbo mode : enabled
turbo mode : enabled
[10:09 xcp-ng-01 ~]#

[10:10 xcp-ng-01 ~]# grep „model name“ /proc/cpuinfo
model name : Intel(R) Celeron(R) J4105 CPU @ 1.50GHz
model name : Intel(R) Celeron(R) J4105 CPU @ 1.50GHz
model name : Intel(R) Celeron(R) J4105 CPU @ 1.50GHz
model name : Intel(R) Celeron(R) J4105 CPU @ 1.50GHz
[10:10 xcp-ng-01 ~]#

[10:10 xcp-ng-01 ~]# xenpm start 1|grep „Avg freq“
Avg freq 2206470 KHz
Avg freq 2311540 KHz
Avg freq 2326550 KHz
Avg freq 2326550 KHz
[10:12 xcp-ng-01 ~]#

Power Settings in Citrix Hypervisor: C-states, Turbo and CPU Frequency Scaling – for AMD processors the „ondemand“ governor is normally preferred as it gives a good compromise between performance and power-saving but Intel processors typically save power by entering deep C-states so the „performance“ governor is preferred

[10:16 xcp-ng-01 ~]# /opt/xensource/libexec/xen-cmdline –set-xen cpufreq=xen:performance
[10:16 xcp-ng-01 ~]#

root@xcp-ng-debian12-01:~# cd XenOrchestraInstallerUpdater

root@xcp-ng-debian12-01:~/XenOrchestraInstallerUpdater# ./xo-install.sh
—————————————–

Welcome to automated Xen Orchestra install

Following options will be used for installation:

OS: Debian 12
Basedir: /opt/xo
User: root
Port: 80
HTTPS: false
Git Branch for source: master
Following plugins will be installed: all
Number of previous installations to preserve: 3
Node.js and yarn auto update: true

Errorlog is stored to /root/XenOrchestraInstallerUpdater/logs/xo-install.log-202401081320 for debug purposes

Depending on which installation is chosen:

Xen Orchestra configuration will be stored to /root/.config/xo-server/config.toml, if you don’t want it to be replaced with every update, set CONFIGUPDATE to false in xo-install.cfg
Xen Orchestra Proxy configuration will be stored to /root/.config/xo-proxy/config.toml. Config won’t be overwritten during update, ever
—————————————–

1. Install
2. Update
3. Rollback
4. Install proxy
5. Update proxy
6. Exit

: 2
[info] Installing nodesource repository

[info] Checking current node.js version

[ok] node.js version already on 18, checking updates

[info] Fetching Xen Orchestra source code

[info] Creating install directory: /opt/xo/xo-builds/xen-orchestra-202401081320

[info] Updating Xen Orchestra from ‚b1e879ca2‘ to ‚ae518399f‘

[info] No 3rd party plugins to install

[info] xo-server and xo-web build takes quite a while. Grab a cup of coffee and lay back

[ok] Running installation

[ok] Installing plugins

[ok] Shutting down running xo-server

[info] Fixing binary path in systemd service configuration file
[info] Adding WorkingDirectory parameter to systemd service configuration file
[info] Replacing systemd service configuration file
[info] Reloading systemd configuration

[info] Fixing relative path to xo-web installation in xo-server configuration file
[info] Changing redis connection address in xo-server configuration file
[info] Activating modified configuration file

[info] Symlinking fresh xo-server install/update to /opt/xo/xo-server
[info] Symlinking fresh xo-web install/update to /opt/xo/xo-web
[info] Symlinking fresh xo-cli install/update to /opt/xo/xo-cli
[info] Symlinking xo-cli script to /usr/local/bin/xo-cli

[info] Starting xo-server…
waiting for port to be open

WebUI started in port 80. Make sure you have firewall rules in place to allow access.

[info] Update successful. Enabling xo-server service to start on reboot

[ok] Removing old inactive installations after update. Leaving 3 latest

root@xcp-ng-debian12-01:~/XenOrchestraInstallerUpdater#

root@xcp-ng-debian12-01:~# apt-get install git

root@xcp-ng-debian12-01:~# git clone https://github.com/ronivay/XenOrchestraInstallerUpdater.git

root@xcp-ng-debian12-01:~# cd XenOrchestraInstallerUpdater

root@xcp-ng-debian12-01:~/XenOrchestraInstallerUpdater# cp sample.xo-install.cfg xo-install.cfg

root@xcp-ng-debian12-01:~/XenOrchestraInstallerUpdater# ./xo-install.sh –install

[ok] Running apt-get update

[ok] Installing build dependencies, redis server, python3-minimal, git, libvhdi-utils, lvm2, nfs-common, cifs-utils, curl, ntfs-3g, dmidecode

[ok] Installing apt-transport-https and ca-certificates packages to support https repos

[ok] Debian 10/11/12, so installing gnupg also

[ok] Installing node.js

[ok] Installing yarn

[ok] Enabling and starting redis service

[ok] Enabling and starting rpcbind service

[info] Creating missing basedir to /opt/xo

[info] Creating missing xo-builds directory to /opt/xo/xo-builds

[info] Fetching Xen Orchestra source code

[info] Creating install directory: /opt/xo/xo-builds/xen-orchestra-202401030920

[info] Installing Xen Orchestra from branch: master – commit: b1e879ca2

[info] No 3rd party plugins to install

[info] xo-server and xo-web build takes quite a while. Grab a cup of coffee and lay back

[ok] Running installation

[ok] Installing plugins

[info] Fixing binary path in systemd service configuration file
[info] Adding WorkingDirectory parameter to systemd service configuration file
[info] Replacing systemd service configuration file
[info] Reloading systemd configuration

[info] Fixing relative path to xo-web installation in xo-server configuration file
[info] Changing redis connection address in xo-server configuration file
[info] Activating modified configuration file

[info] Symlinking fresh xo-server install/update to /opt/xo/xo-server
[info] Symlinking fresh xo-web install/update to /opt/xo/xo-web
[info] Symlinking fresh xo-cli install/update to /opt/xo/xo-cli
[info] Symlinking xo-cli script to /usr/local/bin/xo-cli

[info] Starting xo-server…
waiting for port to be open

WebUI started in port 80. Make sure you have firewall rules in place to allow access.
Default username: admin@admin.net password: admin

[info] Installation successful. Enabling xo-server service to start on reboot

root@xcp-ng-debian12-01:~/XenOrchestraInstallerUpdater#