From 50c243aa590c5c1cb28d5762aef29afddecd3293 Mon Sep 17 00:00:00 2001 From: David Morel Date: Thu, 27 Feb 2025 12:47:02 +0100 Subject: [PATCH 1/2] Adding proxy configuration in the updates documentation Signed-off-by: David Morel --- docs/management/updates.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/docs/management/updates.md b/docs/management/updates.md index 771a7f42..9e4b5a2b 100644 --- a/docs/management/updates.md +++ b/docs/management/updates.md @@ -30,6 +30,31 @@ If your version is lower than `8.2`, it will not receive updates anymore. To kee Your dom0 system must either have access to the internet, or to a local mirror. In the second case, make sure to update the `baseurl` values in `/etc/yum.repos.d/xcp-ng.repo` to make them point at the local mirror, and keep the mirror regularly synced. +#### Proxy configuration + +If your hosts need to use a proxy to be able to access the repositories, there are multiple ways to configure it depending on your use case: + +For all yum repositories: +- Set `proxy=` in `[main]` section of `/etc/yum.conf` + +For specific repositories: +- Set `proxy=` in the repository section of your choice in files present in `/etc/yum.repos.d` + +Set a system-wide proxy that will be used for everything, not only yum: +- Add you can export lines for `http_proxy` and `https_proxy` variables in `/etc/environment` +```bash +export http_proxy= +export https_proxy= +``` + +:::warning +There are caveats for each methods: +- Updating the `yum` package may overwrite `/etc/yum.conf` +- Updating the `xcp-ng-release` package may overwrite files in `/etc/yum.repos.d/` +- Updating the `setup` package may overwrite `/etc/environment` +- Environmentn variables won't be taken into account when updating through Xen Orchestra +::: + ### Be cautious with third party repositories and packages If you have enabled third party repositories (CentOS, EPEL...) in the past, make sure to **disable** them before updating. Otherwise, core packages from your dom0 system can be overwritten with versions of packages that have not been tested in the context of XCP-ng, or lack specific patches. From 2f7cac241587807670037b1f86bdf90dc084e5ea Mon Sep 17 00:00:00 2001 From: David Morel Date: Thu, 27 Feb 2025 12:50:09 +0100 Subject: [PATCH 2/2] Fix typo in kernel module policy Signed-off-by: David Morel --- docs/project/development-process/kernel-module-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/project/development-process/kernel-module-policy.md b/docs/project/development-process/kernel-module-policy.md index 8bd31cc2..823dbd5d 100644 --- a/docs/project/development-process/kernel-module-policy.md +++ b/docs/project/development-process/kernel-module-policy.md @@ -4,7 +4,7 @@ sidebar_position: 9 # Kernel module policy -Our policity about kernel modules. +Our policy about kernel modules. In XCP-ng, there is only one version of the kernel that is supported at a given time. There's also an [alternate kernel](../../../installation/hardware#-alternate-kernel) available for troubleshooting. The policy differs whether the kernel modules are for XCP-ng's supported kernel or for an alternate kernel.