Merge branch 'one-6.10-maintenance' into b-6750

Author: rsmontero

source/intro_release_notes/release_notes/acknowledgements.rst

@@ -6,8 +6,8 @@ Acknowledgements
 
 The OpenNebula project would like to thank the `community members <https://github.com/OpenNebula/one/graphs/contributors>`__ and `users <http://opennebula.io/featuredusers/>`__ who have contributed to this software release by being active in discussions, answering user questions, or providing patches for bugfixes, features, and documentation.
 
-Part of the new functionality in OpenNebula 6.10 has been funded by the following innovation projects:
+Some of the new functionality in OpenNebula 6.10 has been made possible through funding from the following innovation projects:
 
    * `SovereignEdge.Cognit <http://cognit.sovereignedge.eu>`__ (Grant Agreement 101092711), through the European Union’s Horizon Europe Research and Innovation Programme.
-   * `OneEdge5G <http://oneedge5g.eu>`__ (Grant Agreement TSI-064200-2023-1), supported by the Spanish Ministry for Digital Transformation and Civil Service through the UNICO I+D 6G Program, co-funded by the European Union – NextGenerationEU through the Recovery and Resilience Facility (RRF).
-   * `OneNextGen <http://onenextgen.eu>`__ (Grant Agreement UNICO IPCEI-2023-003), supported by the Spanish Ministry for Digital Transformation and Civil Service through the UNICO IPCEI Program, co-funded by the European Union – NextGenerationEU through the Recovery and Resilience Facility (RRF).
+   * `ONEedge5G <http://oneedge5g.eu>`__ (Grant Agreement TSI-064200-2023-1), supported by the Spanish Ministry for Digital Transformation and Civil Service through the UNICO I+D 6G Program, co-funded by the European Union – NextGenerationEU through the Recovery and Resilience Facility (RRF).
+   * `ONEnextgen <http://onenextgen.eu>`__ (Grant Agreement UNICO IPCEI-2023-003), supported by the Spanish Ministry for Digital Transformation and Civil Service through the UNICO IPCEI Program, co-funded by the European Union – NextGenerationEU through the Recovery and Resilience Facility (RRF).

source/intro_release_notes/release_notes_enterprise/resolved_issues_6102.rst

@@ -15,4 +15,7 @@ The following issues has been solved in 6.10.2:
 - `Fix PyOne installation through pip <https://github.com/OpenNebula/one/issues/6784>`__.
 - `Fix the list of attibutes that can be overriden in vmm_exec_kvm.conf <https://github.com/OpenNebula/one/issues/6548>`__.
 - `Fix a rare crash in 'onedb fsck' caused by a locked MarketPlaceApp in a federated environment <https://github.com/OpenNebula/one/issues/6793>`__.
-- `Fix iotune attributes not being passed to VM if value is greater than int capacity <https://github.com/OpenNebula/one/issues/6750>`__.
+- `Fix iotune attributes not being passed to VM if value is a big number <https://github.com/OpenNebula/one/issues/6750>`__.
+- `Fix Sunstone filter VMs on "Locked" gives empty white page <https://github.com/OpenNebula/one/issues/6768>`__.
+- `Fix Sunstone host graph not showing information <https://github.com/OpenNebula/one/issues/6788>`__.
+- `Fix SecurityGroup rule validation logic to include additional checks for port ranges <https://github.com/OpenNebula/one/issues/6759>`__.

source/management_and_operations/network_management/overview.rst

@@ -10,7 +10,7 @@ How Should I Read This Chapter
 Before reading this chapter, you should have already installed and configured your cloud. The Chapter is structured as follows:
 
   - The :ref:`Virtual Networks <manage_vnets>` and :ref:`Virtual Networks Templates <vn_templates>` explain how to create networks.
-  - Regular users can self-provision virtual networks for their use. ref:`The details are explained here <self_provision>`.
+  - The :ref:`Self Provision <self_provision>` section details how regular users can self-provision virtual networks for their use.
   - You will also find information on :ref:`Security Groups <security_groups>`, to easily define firewall rules.
   - Additionally you will learn on how to manage :ref:`Virtual Routers <vrouter>` which are an OpenNebula resource that provide routing across Virtual Networks.
 

source/open_cluster_deployment/storage_setup/nas_ds.rst

@@ -4,22 +4,24 @@
 NFS/NAS Datastores
 ================================================================================
 
-This storage configuration assumes that your Hosts can access and mount a shared volume located on a NAS (Network Attached Storage) server. You will use this shared volumes to store VM disk images files. The Virtual Machines will boot also from the shared volume.
+This storage configuration assumes that your Hosts can access and mount a shared volume located on a NAS (Network Attached Storage) server. You will use this shared volume to store VM disk images files. The Virtual Machines will boot also from the shared volume.
 
-The scalability of this solution is bounded to the performance of your NAS server. However you can use multiple NAS server simultaneously to improve the scalability of your OpenNebula cloud. The use of multiple NFS/NAS datastores will let you:
+The scalability of this solution will be bound to the performance of your NAS server. However, you can use multiple NAS server simultaneously to improve the scalability of your OpenNebula cloud. The use of multiple NFS/NAS datastores will allow you to:
 
 * Balance I/O operations between storage servers.
-* Apply different SLA policies (e.g., backup) to different VM types or users.
+* Apply different SLA policies (e.g. backup) to different VM types or users.
 * Easily add new storage.
 
+Using an NFS/NAS Datastore provides a straightforward solution for implementing thin provisioning for VMs, which is enabled by default when using the **qcow2** image format.
+
 Front-end Setup
 ================================================================================
 
 Simply mount the **Image** Datastore directory in the Front-end in ``/var/lib/one/datastores/<datastore_id>``. Note that if all the Datastores are of the same type you can mount the whole ``/var/lib/one/datastores`` directory.
 
 .. note:: The Front-end only needs to mount the Image Datastores and **not** the System Datastores.
 
-.. note::  **NFS volumes mount tips**. The following options are recommended to mount NFS shares:``soft, intr, rsize=32768, wsize=32768``. With the documented configuration of libvirt/kvm the image files are accessed as ``oneadmin`` user. If the files must be read by ``root``, the option ``no_root_squash`` must be added.
+.. note::  **NFS volumes mount tips**. The following options are recommended to mount NFS shares:``soft, intr, rsize=32768, wsize=32768``. With the documented configuration of libvirt/kvm, the image files can be accessed as the ``oneadmin`` user. If the files must be read by ``root``, the option ``no_root_squash`` must be added.
 
 Host Setup
 ================================================================================
@@ -30,7 +32,7 @@ The configuration is the same as for the Front-end above: simply mount in each H
 
 OpenNebula Configuration
 ================================================================================
-Once the Host and Front-end storage is setup, the OpenNebula configuration comprises the creation of an Image and System Datastores.
+Once Host and Front-end storage have been is set up, the OpenNebula configuration comprises the creation of an Image and System Datastores.
 
 Create System Datastore
 --------------------------------------------------------------------------------