Merge branch 'master' into sec-platform

rsmontero · web-flow · commit 6f14b38fba53 · 2025-02-20T10:51:06.000+01:00
diff --git a/source/installation_and_configuration/opennebula_services/fireedge.rst b/source/installation_and_configuration/opennebula_services/fireedge.rst
@@ -33,12 +33,16 @@ Main Features
 Configuration
 ================================================================================
 
-The FireEdge server configuration file can be found in ``/etc/one/fireedge-server.conf`` on your Front-end. It uses **YAML** syntax with following parameters:
+The FireEdge server configuration file can be found in ``/etc/one/fireedge-server.conf`` on your Front-end. It uses the **YAML** syntax, with the parameters listed in the table below.
 
 .. note::
 
     After a configuration change, the FireEdge server must be :ref:`restarted <fireedge_conf_service>` to take effect.
 
+.. tip::
+
+    For a quick view of any changes in configuration file options in maintenance releases, check the Resolved Issues page in the :ref:`Release Notes <rn_enterprise>` for the release. Please note that even in the case of changes (such as a new option available), you do *not* need to update your configuration files unless you wish to change the application's behavior.
+
 +-------------------------------------------+--------------------------------+----------------------------------------------------+
 | Parameter                                 | Default Value                  | Description                                        |
 +===========================================+================================+====================================================+
@@ -294,4 +298,4 @@ If another service is using the port, you can change FireEdge configuration (``/
 .. |fireedge_sunstone_linux_drawer_logo| image:: /images/fireedge_drawer_linux_logo.png
    :width: 45%
 .. |fireedge_sunstone_list_datatable| image:: /images/sunstone_list_datatable.png
-.. |fireedge_sunstone_setting_list_datatable| image:: /images/sunstone_setting_list_datatable.png
+.. |fireedge_sunstone_setting_list_datatable| image:: /images/sunstone_setting_list_datatable.png
diff --git a/source/installation_and_configuration/opennebula_services/monitoring.rst b/source/installation_and_configuration/opennebula_services/monitoring.rst
@@ -27,7 +27,11 @@ If information stops coming from a specific Host, OpenNebula detects it by missi
 Configuration
 =============
 
-The monitor daemon (``onemonitord``) is configured in ``/etc/one/monitord.conf``. The following table describes the configuration attributes for it:
+The monitor daemon (``onemonitord``) is configured in ``/etc/one/monitord.conf``. The table below describes the file's configuration attributes.
+
+.. tip::
+
+    For a quick view of any changes in configuration file options in maintenance releases, check the Resolved Issues page in the :ref:`Release Notes <rn_enterprise>` for the release. Please note that even in the case of changes (such as a new option available), you do *not* need to update your configuration files unless you wish to change the application's behavior.
 
 +---------------------+---------------------+------------------------------------------------------------------------------------+
 | Parameter           | Attribute           | Description                                                                        |
diff --git a/source/installation_and_configuration/opennebula_services/oned.rst b/source/installation_and_configuration/opennebula_services/oned.rst
@@ -9,12 +9,16 @@ The OpenNebula Daemon (``oned``) is the **core service of the cloud management p
 Configuration
 =============
 
-The OpenNebula Daemon configuration file can be found in ``/etc/one/oned.conf`` on the Front-end and can be customized with the following parameters:
+The OpenNebula Daemon configuration file can be found in ``/etc/one/oned.conf`` on the Front-end, and can be customized with the parameters listed in the table below.
 
 .. note::
 
     After a configuration change, the OpenNebula Daemon must be :ref:`restarted <oned_conf_service>` to take effect.
 
+.. tip::
+
+    For a quick view of any changes in configuration file options in maintenance releases, check the Resolved Issues page in the :ref:`Release Notes <rn_enterprise>` for the release. Please note that even in the case of changes (such as a new option available), you do *not* need to update your configuration files unless you wish to change the application's behavior.
+
 -  ``MANAGER_TIMER``: Time in seconds the core uses to evaluate periodical functions. ``MONITORING_INTERVAL`` cannot have a smaller value than ``MANAGER_TIMER``.
 -  ``MONITORING_INTERVAL_DATASTORE``: Time in seconds between each Datastore monitoring cycle.
 -  ``MONITORING_INTERVAL_MARKET``: Time in seconds between each Marketplace monitoring cycle.
diff --git a/source/installation_and_configuration/opennebula_services/oneflow.rst b/source/installation_and_configuration/opennebula_services/oneflow.rst
@@ -12,12 +12,16 @@ Read more in :ref:`Multi-VM Service Management <multivm_service_management>`.
 Configuration
 =============
 
-The OneFlow configuration file can be found in ``/etc/one/oneflow-server.conf`` on your Front-end. It uses **YAML** syntax with following parameters:
+The OneFlow configuration file can be found in ``/etc/one/oneflow-server.conf`` on your Front-end. It uses the **YAML** syntax, with the parameters listed in the table below.
 
 .. note::
 
     After a configuration change, the OneFlow server must be :ref:`restarted <oneflow_conf_service>` to take effect.
 
+.. tip::
+
+    For a quick view of any changes in configuration file options in maintenance releases, check the Resolved Issues page in the :ref:`Release Notes <rn_enterprise>` for the release. Please note that even in the case of changes (such as a new option available), you do *not* need to update your configuration files unless you wish to change the application's behavior.
+
 +---------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 |       Parameter           |                                                                               Description                                                                               |
 +===========================+=========================================================================================================================================================================+
diff --git a/source/installation_and_configuration/opennebula_services/onegate.rst b/source/installation_and_configuration/opennebula_services/onegate.rst
@@ -18,12 +18,16 @@ To use the OneGate Service, VMs must have connectivity to the service. We recomm
 Configuration
 =============
 
-The OneGate configuration file can be found in ``/etc/one/onegate-server.conf`` on your Front-end. It uses **YAML** syntax with following parameters:
+The OneGate configuration file can be found in ``/etc/one/onegate-server.conf`` on your Front-end. It uses the **YAML** syntax, with the parameters listed in the table below.
 
 .. note::
 
     After a configuration change, the OneGate server must be :ref:`restarted <onegate_conf_service>` to take effect.
 
+.. tip::
+
+    For a quick view of any changes in configuration file options in maintenance releases, check the Resolved Issues page in the :ref:`Release Notes <rn_enterprise>` for the release. Please note that even in the case of changes (such as a new option available), you do *not* need to update your configuration files unless you wish to change the application's behavior.
+
 +-------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 |       Parameter               |                                                                               Description                                                                               |
 +===============================+=========================================================================================================================================================================+
diff --git a/source/installation_and_configuration/opennebula_services/scheduler.rst b/source/installation_and_configuration/opennebula_services/scheduler.rst
@@ -35,12 +35,16 @@ The policy used to place a VM can be configured in two places:
 Configuration
 =============
 
-The Scheduler configuration file is in ``/etc/one/sched.conf`` on the Front-end and can be adapted to your needs with the following parameters:
+The Scheduler configuration file is ``/etc/one/sched.conf`` on the Front-end, and can be customized with the parameters listed in the table below.
 
 .. note::
 
     After a configuration change, the OpenNebula Scheduler must be :ref:`restarted <sched_conf_service>` to take effect.
 
+.. tip::
+
+    For a quick view of any changes in configuration file options in maintenance releases, check the Resolved Issues page in the :ref:`Release Notes <rn_enterprise>` for the release. Please note that even in the case of changes (such as a new option available), you do *not* need to update your configuration files unless you wish to change the application's behavior.
+
 * ``MESSAGE_SIZE``: Buffer size in bytes for XML-RPC responses (Default: ``1073741824``).
 * ``TIMEOUT``: Seconds to timeout XML-RPC calls to oned (Default: ``60``).
 * ``ONE_XMLRPC``: Endpoint of the OpenNebula XML-RPC API (Default: ``http://localhost:2633/RPC2``)
diff --git a/source/intro_release_notes/release_notes/arm64_beta.rst b/source/intro_release_notes/release_notes/arm64_beta.rst
@@ -0,0 +1,11 @@
+.. _arm64:
+
+================================================================================
+ARM64 packages
+================================================================================
+
+6.10.3-EE and 6.10.0.1-CE release includes ARM64 packages for all supported operating systems.
+
+These ARM packages are being released in beta mode, allowing the community to test them and provide feedback. This initiative aims to extend OpenNebula’s flexibility by enabling deployment on ARM-based servers (both hypervisors and front-end nodes), opening new possibilities for lightweight, distributed cloud environments.
+
+For the configuration details about ARM64 please refer :ref:`ARM64 specific <arm64specifics>`
diff --git a/source/intro_release_notes/release_notes/index.rst b/source/intro_release_notes/release_notes/index.rst
@@ -9,6 +9,7 @@ Release Notes |version|
 
    What's New <whats_new>
    Platform Notes <platform_notes>
+   ARM64 packages <arm64>
    Compatibility Guide <compatibility>
    Known Issues <known_issues>
    Acknowledgements <acknowledgements>
diff --git a/source/intro_release_notes/release_notes/whats_new.rst b/source/intro_release_notes/release_notes/whats_new.rst
@@ -54,6 +54,7 @@ Additionally, the following functionalities are present that were not in OpenNeb
 - `Fix de-selecting hidden datatable entries <https://github.com/OpenNebula/one/issues/6781>`__.
 - `Text of selection in schedule action <https://github.com/OpenNebula/one/issues/6410>`__.
 - `Fix Filter datastore type when deploy a VM <https://github.com/OpenNebula/one/issues/6927>`__.
+- `Fix show more labels in cards <https://github.com/OpenNebula/one/issues/6643>`__.
 
 Other Issues Solved
 ================================================================================
diff --git a/source/open_cluster_deployment/kvm_node/kvm_driver.rst b/source/open_cluster_deployment/kvm_node/kvm_driver.rst
@@ -9,6 +9,8 @@ Requirements
 
 The Hosts will need a CPU with `Intel VT <http://www.intel.com/content/www/us/en/virtualization/virtualization-technology/intel-virtualization-technology.html>`__ or `AMD's AMD-V <http://www.amd.com/en-us/solutions/servers/virtualization>`__ features in order to support virtualization. KVM's `Preparing to use KVM <http://www.linux-kvm.org/page/FAQ#Preparing_to_use_KVM>`__ guide will clarify any doubts you may have regarding whether your hardware supports KVM.
 
+Also, since OpenNebula 6.10.3-EE and 6.10.0.1-CE ARM64 architecture is supported (in beta mode).
+
 KVM will be installed and configured after following the :ref:`KVM Host Installation <kvm_node>` section.
 
 Considerations & Limitations
@@ -192,7 +194,7 @@ NIC
 
     $ virsh -c qemu:///system nwfilter-list
 
-* ``VIRTIO_QUEUES`` to define how many queues will be used for the communication between CPUs and Network drivers. This attribute is only available with ``MODEL="virtio"``.
+* ``VIRTIO_QUEUES`` to define how many queues will be used for the communication between CPUs and Network drivers. This attribute is only available with ``MODEL="virtio"``. The ``auto`` keyword automatically set the number of queues to the number of vCPUs.
 
 Graphics
 ~~~~~~~~
@@ -615,6 +617,38 @@ The parameters that can be changed here are as follows:
 
 See the :ref:`Virtual Machine drivers reference <devel-vmm>` for more information.
 
+
+.. _arm64specifics:
+
+ARM64 Specifics
+===============
+
+We suggest the following adjustments for the ARM64 architecture. In ``/etc/one/oned.conf``, switch to ``sd`` or ``vd`` for the CD-ROM device:
+
+.. code::
+
+    DEFAULT_CDROM_DEVICE_PREFIX = "sd"
+
+This is necessary as IDE disk support is usually missing in ARM64.
+
+Additionally, we recommend adding a virtio keyboard using the ``RAW`` attribute in ``/etc/one/vmm_exec/vmm_exec_kvm.conf`` to ensure keyboard functionality over VNC:
+
+.. code::
+
+    RAW = "<devices><input type='keyboard' bus='virtio'/></devices>"
+
+The following OS section is recommended for an ARM64 host template. Here, ``virt`` is typically an alias for the most recent ``QEMU ARM Virtual Machine``:
+
+.. code::
+
+   OS=[
+     ARCH="aarch64",
+     FIRMWARE="/usr/share/AAVMF/AAVMF_CODE.fd",
+     FIRMWARE_SECURE="no",
+     MACHINE="virt"
+   ]
+
+
 Troubleshooting
 ===============
 
diff --git a/source/open_cluster_deployment/kvm_node/kvm_node_installation.rst b/source/open_cluster_deployment/kvm_node/kvm_node_installation.rst
@@ -18,8 +18,8 @@ Step 1. Add OpenNebula Repositories
 Step 2. Installing the Software
 ===============================
 
-Installing on CentOS/RHEL
--------------------------
+Installing on AlmaLinux/RHEL
+----------------------------
 
 .. include:: ../common_node/epel.txt
 
@@ -57,7 +57,7 @@ Step 3. Host OS Security Configuration (Optional)
 
     If you are performing an upgrade skip this and the next steps and go back to the upgrade document.
 
-Disable SELinux on CentOS/RHEL
+Disable SELinux on AlmaLinux/RHEL
 ------------------------------------------
 
 .. include:: ../common_node/selinux.txt
diff --git a/source/open_cluster_deployment/kvm_node/overview.rst b/source/open_cluster_deployment/kvm_node/overview.rst
@@ -4,7 +4,7 @@
 Overview
 ================================================================================
 
-`KVM <https://www.linux-kvm.org/>`__ (Kernel-based Virtual Machine) is the main virtualization solution for Linux on x86 hardware that contains virtualization extensions (Intel VT or AMD-V). It consists of the loadable KVM kernel modules (one that provides the core virtualization infrastructure and several processor-specific modules), but the complete KVM virtualization stack usually also contains the user-space machine hardware emulator `QEMU <https://www.qemu.org>`__ accelerated by the KVM and virtual machines management tool `libvirt <https://libvirt.org>`__.
+`KVM <https://www.linux-kvm.org/>`__ (Kernel-based Virtual Machine) is the main virtualization solution for Linux on x86 hardware that contains virtualization extensions (Intel VT or AMD-V) and on ARM64 (currently in beta mode). It consists of the loadable KVM kernel modules (one that provides the core virtualization infrastructure and several processor-specific modules), but the complete KVM virtualization stack usually also contains the user-space machine hardware emulator `QEMU <https://www.qemu.org>`__ accelerated by the KVM and virtual machines management tool `libvirt <https://libvirt.org>`__.
 
 By using KVM, you can run multiple Virtual Machines with unmodified Linux or Windows images. Each Virtual Machine has private virtualized hardware - network card, disk, graphics adapter, etc.
 
