diff --git a/content/getting_started/install_opennebula/evaluation/deploy_opennebula_onprem_with_minione.md b/content/getting_started/install_opennebula/evaluation/deploy_opennebula_onprem_with_minione.md index e5708f565..d36dba937 100644 --- a/content/getting_started/install_opennebula/evaluation/deploy_opennebula_onprem_with_minione.md +++ b/content/getting_started/install_opennebula/evaluation/deploy_opennebula_onprem_with_minione.md @@ -53,7 +53,7 @@ To run the miniONE script, you will need a physical server with a fresh installa : - RHEL/AlmaLinux 9 or 10 - Debian 12 or 13 - Ubuntu 24.04 or 26.04 - - openSUSE 16.0, SLES 15.7 + - openSUSE 16.0, SLES 16.0 **Minimum hardware:** : - 32 GiB RAM diff --git a/content/getting_started/install_opennebula/production/minione_frontend_install.md b/content/getting_started/install_opennebula/production/minione_frontend_install.md index 7387be8d0..0f5b7b218 100644 --- a/content/getting_started/install_opennebula/production/minione_frontend_install.md +++ b/content/getting_started/install_opennebula/production/minione_frontend_install.md @@ -30,7 +30,7 @@ To install miniONE it is important to meet the following prerequisites for the m * RHEL/AlmaLinux 9 or 10 * Debian 12 or 13 * Ubuntu 24.04 or 26.04 -* openSUSE 16.0, SLES 15.7 +* openSUSE 16.0, SLES 16.0 * See the [Platform Notes]({{% relref "software/release_information/release_notes/platform_notes.md" %}}) for further details on compatible operating systems **Minimum hardware:** diff --git a/content/product/integration_references/infrastructure_drivers_development/interactive_backup.md b/content/product/integration_references/infrastructure_drivers_development/interactive_backup.md index af8789e65..64ead34d2 100644 --- a/content/product/integration_references/infrastructure_drivers_development/interactive_backup.md +++ b/content/product/integration_references/infrastructure_drivers_development/interactive_backup.md @@ -601,6 +601,3 @@ OneBEX uses exporters to expose VM disk data to external backup systems. |----------|-----------------|-----------|-------------| | `nbd` | File-based `qcow2` disks | Network Block Device | Exposes the backup disk through NBD. OneBEX starts a read-only `qemu-nbd` process and serves the disk export through a Unix socket. | | `lvm` | Disks on LVM datastores | Direct block-device reads | Exposes the prepared LVM block device directly. Full backups return the full device extent. Incremental backups use `thin_delta` to return changed extents from LVM thin metadata. | - -{{< alert title="Note" type="info" >}} -The `nbd` exporter reads disk data with the `nbdsh` tool from the `python3-libnbd` package. This package is installed automatically as a dependency of `opennebula-node-kvm` on all supported platforms except SLES 15, where it is not available in the SUSE repositories. To use the `nbd` exporter on SLES 15 hosts, install `python3-libnbd` manually, for example from the openSUSE Leap 15.6 repositories, together with the matching `libnbd0` package. {{< /alert >}} diff --git a/content/software/installation_process/frontend_installation/frontend_install.md b/content/software/installation_process/frontend_installation/frontend_install.md index 051a1c7e1..f674f98e7 100644 --- a/content/software/installation_process/frontend_installation/frontend_install.md +++ b/content/software/installation_process/frontend_installation/frontend_install.md @@ -81,7 +81,7 @@ Available packages for OpenNebula clients, the Front-end and hypervisor nodes: | **opennebula-common** | Shared content for OpenNebula packages | | **opennebula-common-onecfg** | Helpers for [Configuration Management]({{% relref "software/upgrade_process/configuration_management_ee/" %}}) tool | | rpm: **opennebula-java**

deb: **libopennebula-java**

deb: **libopennebula-java-doc** | [Java OCA]({{% relref "/product/integration_references/system_interfaces/java#java" %}}) Bindings | -| **python3-pyone** | [Python 3 OCA]({{% relref "/product/integration_references/system_interfaces/python#python" %}}) Bindings | +| **python3-pyone**

SLES/openSUSE: **python313-pyone** | [Python 3 OCA]({{% relref "/product/integration_references/system_interfaces/python#python" %}}) Bindings | There are also packages with debugging symbols for some platforms, e.g., `openenbula-debuginfo` on AlmaLinux/RHEL and `opennebula-dbgsym` on Debian/Ubuntu. Other architecture-specific components might come with similarly named packages, please check your packaging database if necessary. diff --git a/content/software/installation_process/frontend_installation/opennebula_repository_configuration_ce.md b/content/software/installation_process/frontend_installation/opennebula_repository_configuration_ce.md index 892fcfa9d..1ab233206 100644 --- a/content/software/installation_process/frontend_installation/opennebula_repository_configuration_ce.md +++ b/content/software/installation_process/frontend_installation/opennebula_repository_configuration_ce.md @@ -112,16 +112,14 @@ apt-get update ### SUSE -#### SUSE Linux Enterprise Server 15 SP7 +#### SUSE Linux Enterprise Server 16 -Execute the following commands as user `root`: +SUSE Linux Enterprise Server 16 requires the OpenNebula repository and the SUSE Package Hub extension. Execute the following commands as user `root`: ```shell arch=$(uname -m) -SUSEConnect -p PackageHub/15.7/$arch -SUSEConnect -p sle-module-public-cloud/15.7/$arch -SUSEConnect -p sle-module-desktop-applications/15.7/$arch +SUSEConnect -p PackageHub/16.0/$arch rpm --import https://downloads.opennebula.io/repo/repo2.key @@ -130,7 +128,7 @@ cat << "EOT" > /etc/zypp/repos.d/opennebula.repo name=OpenNebula Community Edition enabled=1 autorefresh=1 -baseurl=https://downloads.opennebula.io/repo/{{< release >}}/SLES/15/$basearch +baseurl=https://downloads.opennebula.io/repo/{{< release >}}/SLES/16/$basearch gpgkey=https://downloads.opennebula.io/repo/repo2.key gpgcheck=1 repo_gpgcheck=1 @@ -139,6 +137,14 @@ EOT zypper refresh ``` +{{< alert title="Note" type="info" >}} +The Python bindings package `python313-pyone` depends on `python313-grpcio`, which is not shipped in the SLES base product or in Package Hub, but in the SUSE Linux Enterprise High Availability Extension. To install `python313-pyone` on SLES 16, register the extension first (an additional registration code is required): + +```shell +SUSEConnect -p sle-ha/16.0/$(uname -m) -r +``` +{{< /alert >}} + #### openSUSE Leap 16.0 openSUSE Leap 16.0 requires the OpenNebula repository and the openSUSE Science repository for SciPy. Execute the following as user `root`: diff --git a/content/software/installation_process/frontend_installation/opennebula_repository_configuration_ee.md b/content/software/installation_process/frontend_installation/opennebula_repository_configuration_ee.md index acb79601b..6b6033d89 100644 --- a/content/software/installation_process/frontend_installation/opennebula_repository_configuration_ee.md +++ b/content/software/installation_process/frontend_installation/opennebula_repository_configuration_ee.md @@ -147,16 +147,14 @@ apt-get update ### SUSE -#### SUSE Linux Enterprise Server 15 SP7 +#### SUSE Linux Enterprise Server 16 -Execute the following as user `root`: +SUSE Linux Enterprise Server 16 requires the OpenNebula repository and the SUSE Package Hub extension. Execute the following as user `root`: ```shell arch=$(uname -m) -SUSEConnect -p PackageHub/15.7/$arch -SUSEConnect -p sle-module-desktop-applications/15.7/$arch -SUSEConnect -p sle-module-public-cloud/15.7/$arch +SUSEConnect -p PackageHub/16.0/$arch rpm --import https://downloads.opennebula.io/repo/repo2.key @@ -172,7 +170,7 @@ cat << "EOT" > /etc/zypp/repos.d/opennebula.repo name=OpenNebula Enterprise Edition enabled=1 autorefresh=1 -baseurl=https://enterprise.opennebula.io/repo/{{< release >}}/SLES/15/$basearch?credentials=opennebula.conf +baseurl=https://enterprise.opennebula.io/repo/{{< release >}}/SLES/16/$basearch?credentials=opennebula.conf gpgkey=https://downloads.opennebula.io/repo/repo2.key gpgcheck=1 repo_gpgcheck=1 @@ -181,6 +179,14 @@ EOT zypper refresh ``` +{{< alert title="Note" type="info" >}} +The Python bindings package `python313-pyone` depends on `python313-grpcio`, which is not shipped in the SLES base product or in Package Hub, but in the SUSE Linux Enterprise High Availability Extension. To install `python313-pyone` on SLES 16, register the extension first (an additional registration code is required): + +```shell +SUSEConnect -p sle-ha/16.0/$(uname -m) -r +``` +{{< /alert >}} + #### openSUSE Leap 16.0 openSUSE Leap 16.0 requires the OpenNebula repository and the openSUSE Science repository for SciPy. Execute the following as user `root`: diff --git a/content/software/installation_process/frontend_installation/overview.md b/content/software/installation_process/frontend_installation/overview.md index 72519f947..0df959c80 100644 --- a/content/software/installation_process/frontend_installation/overview.md +++ b/content/software/installation_process/frontend_installation/overview.md @@ -68,7 +68,7 @@ Regardless of the method chosen, you must ensure that your Host meets the minimu * RHEL/AlmaLinux 9 or 10 * Debian 12 or 13 * Ubuntu 24.04 or 26.04 -* openSUSE 16.0, SLES 15.7 +* openSUSE 16.0, SLES 16.0 * See the [Platform Notes]({{% relref "software/release_information/release_notes/platform_notes.md" %}}) for further details on compatible operating systems **Minimum hardware:** diff --git a/content/software/release_information/release_notes/platform_notes.md b/content/software/release_information/release_notes/platform_notes.md index ac28a836b..377f30fd4 100644 --- a/content/software/release_information/release_notes/platform_notes.md +++ b/content/software/release_information/release_notes/platform_notes.md @@ -30,7 +30,7 @@ For supported deployments, hypervisor nodes in the same Cluster must run the sam | Rocky Linux | 9, 10 | [Front-end Installation]({{% relref "frontend_install" %}}).
Available through Red Hat packages. | | Ubuntu Server | 24.04 (LTS), 26.04 (LTS) | [Front-end Installation]({{% relref "frontend_install" %}}) | | Debian | 12, 13 | [Front-end Installation]({{% relref "frontend_install" %}}) | -| SUSE Linux Enterprise | 15 | [Front-end Installation]({{% relref "frontend_install" %}}) | +| SUSE Linux Enterprise | 16 | [Front-end Installation]({{% relref "frontend_install" %}}) | | openSUSE | 16 | [Front-end Installation]({{% relref "frontend_install" %}}) | | MariaDB or MySQL | Version included in the Linux distribution | [MySQL Setup]({{% relref "software/installation_process/frontend_installation/database#mysql" %}}) | | SQLite | Version included in the Linux distribution | Default DB, no configuration needed | @@ -47,7 +47,7 @@ Support for nodes’ operating system ensures that the latest two LTS releases f | Rocky Linux | 9, 10 | [KVM Driver]({{% relref "../../../product/operation_references/hypervisor_configuration/kvm_driver#kvmg" %}}).
Available through Red Hat packages. | | Ubuntu Server | 24.04 (LTS), 26.04 (LTS) | [KVM Driver]({{% relref "../../../product/operation_references/hypervisor_configuration/kvm_driver#kvmg" %}}) | | Debian | 12, 13 | [KVM Driver]({{% relref "../../../product/operation_references/hypervisor_configuration/kvm_driver#kvmg" %}}) | -| SUSE Linux Enterprise | 15 | [KVM Driver]({{% relref "../../../product/operation_references/hypervisor_configuration/kvm_driver#kvmg" %}}) | +| SUSE Linux Enterprise | 16 | [KVM Driver]({{% relref "../../../product/operation_references/hypervisor_configuration/kvm_driver#kvmg" %}}) | | openSUSE | 16 | [KVM Driver]({{% relref "../../../product/operation_references/hypervisor_configuration/kvm_driver#kvmg" %}}) | | KVM/Libvirt | Support for version included in the Linux distribution. | [KVM Node Installation]({{% relref "kvm_node_installation#kvm-node" %}}) | diff --git a/content/software/release_information/release_notes/resolved_issues_741.md b/content/software/release_information/release_notes/resolved_issues_741.md index e558ae806..2f9731af0 100644 --- a/content/software/release_information/release_notes/resolved_issues_741.md +++ b/content/software/release_information/release_notes/resolved_issues_741.md @@ -34,6 +34,7 @@ Include a high-level description and a link to the documentation explaining the * Add support for [OneKS deployments in air-gapped environments]({{% relref "platform_services/oneks/management/configuration/#air-gapped-environments" %}}) by allowing appliance auto-import to be disabled and manually imported appliances to be discovered [#7984](https://github.com/OpenNebula/one/issues/7984). * Extend [PCI network Physical Function (PF) control]({{% relref "product/cluster_configuration/pci_passthrough_sriov/network_interfaces#legacy-and-switchdev-modes" %}}) to support PF flags in switchdev mode [#7679](https://github.com/OpenNebula/one/issues/7679). * Bring up network [Physical Functions when using Virtual Functions]({{% relref "product/cluster_configuration/pci_passthrough_sriov/network_interfaces#physical-functions-and-virtual-functions" %}}) as PCI network interfaces, regardless of the SR-IOV mode [#7679](https://github.com/OpenNebula/one/issues/7679). +* Add OpenNebula packages for [SUSE Linux Enterprise Server 16]({{% relref "software/installation_process/frontend_installation/opennebula_repository_configuration_ce/#suse" %}}), which replaces SUSE Linux Enterprise Server 15 as a supported platform (see [Platform Notes]({{% relref "platform_notes" %}})). ## Resolved Issues diff --git a/content/software/upgrade_process/upgrade_guide/upgrading_single.md b/content/software/upgrade_process/upgrade_guide/upgrading_single.md index 1ea039b58..1c6897dab 100644 --- a/content/software/upgrade_process/upgrade_guide/upgrading_single.md +++ b/content/software/upgrade_process/upgrade_guide/upgrading_single.md @@ -86,8 +86,8 @@ zypper refresh zypper update opennebula opennebula-gate opennebula-flow opennebula-fireedge opennebula-form opennebula-guacd opennebula-migration python313-pyone ``` -{{< alert title="Warning" type="warning" >}} -The Python bindings package is named after the Python version of the distribution: use `python313-pyone` on openSUSE 16 and `python311-pyone` on SLES 15. {{< /alert >}} +{{< alert title="Note" type="info" >}} +On SLES/openSUSE the Python bindings package is named after the Python version of the distribution, `python313-pyone`. {{< /alert >}} ### Step 7. Update Configuration Files