Merge branch 'one-5.6-maintenance' into one-5.6

Author: Tino Vazquez

source/conf.py

@@ -66,7 +66,7 @@
 # The short X.Y version.
 version = '5.6'
 # The full version, including alpha/beta/rc tags.
-release = '5.6.1'
+release = '5.6.2'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

source/deployment/vmware_infrastructure_setup/datastore_setup.rst

@@ -42,7 +42,6 @@ Limitations
 
 * When a vCenter template or wild VM is imported into OpenNebula, the virtual disks are imported, an images are created in OpenNebula representing those virtual disks. Although these images represent files that already exist in the datastores, OpenNebula accounts the size of those imported images as if they were new created files and therefore the datastore capacity is decreased even though no real space in the vCenter datastore is being used by the OpenNebula images. You should understand this limitation if for example an image cannot be imported as OpenNebula reports that no more space is left or if you're using disk quotas.
 * No support for disk snapshots in the vCenter datastore.
-* Image names and paths cannot contain spaces or non ASCII characters.
 
 
 The vCenter Transfer Manager

source/intro_release_notes/release_notes/known_issues.rst

@@ -92,5 +92,4 @@ vCenter
 * `#2230 <https://github.com/OpenNebula/one/issues/2230>`_ vCenter driver migrate feedback
 * `#2275 <https://github.com/OpenNebula/one/issues/2275>`_ Remove disk not affected by snap on vCenter
 * `#2254 <https://github.com/OpenNebula/one/issues/2254>`_ spurios syntax help on onehost delete
-* `#2084 <https://github.com/OpenNebula/one/issues/2084>`_ vCenter Cache thread safe (thin related)
-* `#1699 <https://github.com/OpenNebula/one/issues/1699>`_ Wild VM monitoring should not return datastores that contain only swap files
+* `#2084 <https://github.com/OpenNebula/one/issues/2084>`_ vCenter Cache thread safe (thin related)

source/intro_release_notes/release_notes_hotfix/index.rst

@@ -0,0 +1,11 @@
+.. _rn_hotfix:
+
+================================================================================
+Release Notes 5.6.2 Hotfix
+================================================================================
+
+.. toctree::
+   :maxdepth: 1
+
+   What is? <what_is_hotfix>
+   Resolved Issues in 5.6.2 <resolved_issues_562>

source/intro_release_notes/release_notes_hotfix/resolved_issues_562.rst

@@ -0,0 +1,36 @@
+.. _resolved_issues_562:
+
+Resolved Issues in 5.6.2
+--------------------------------------------------------------------------------
+
+A complete list of solved issues for 5.6.2 can be found in the `project development portal <https://github.com/OpenNebula/one/milestone/21>`__.
+
+The following new features has been backported to 5.6.2:
+
+- New option for image datastores to further restrict the system datastores that can be used. This is useful when some system datastores in a cluster can only be used with one image datastore, e.g. use of different pools in Ceph. See `link <https://github.com/OpenNebula/one/issues/2246>`__ and :ref:`datastore definition attributes <ds_op_common_attributes>`.
+- Add support to rename disk snapshots
+
+The following issues has been solved in 5.6.2:
+
+- `Fix issue when setting an specific CPU model <https://github.com/OpenNebula/one/issues/1688>`__.
+- `Fix paginated CLI output for onehost show and oneimage show <https://github.com/OpenNebula/one/issues/2445>`__.
+- `Monitoring VMs fails when there is not datastore associated <https://github.com/OpenNebula/one/issues/2433>`__.
+- `Label icons does not displayed <https://github.com/OpenNebula/one/issues/2473>`__.
+- `Active disk snapshot is missing arrow in Sunstone <https://github.com/OpenNebula/one/issues/2439>`__.
+- `VCENTER_ESX_HOST fail with DRS in vCenter <https://github.com/OpenNebula/one/issues/2477>`__.
+- `vCenter datastores with spaces does not work properly <https://github.com/OpenNebula/one/issues/2437>`__.
+- `tm_mad does not allow disks with brackets <https://github.com/OpenNebula/one/issues/2420>`__.
+- `vCenter uploader change original filename <https://github.com/OpenNebula/one/issues/2464>`__.
+
+Sunstone Note
+--------------------------------------------------------------------------------
+
+There is the new VM autorefresh feature, activated by default at 10 seconds. If you want to change the autorefresh value, you must add the following line in ``vms-tab`` in the different views:
+
+.. code-block:: yaml
+
+    actions:
+        VM.refresh: true
+        ...
+        VM.menu_labels: true
+    autorefresh_info: 5000 # ms

source/intro_release_notes/release_notes_hotfix/what_is_hotfix.rst

@@ -0,0 +1,13 @@
+.. _whats_is_hotfix:
+
+================================================================================
+What's a HotFix Release?
+================================================================================
+
+A hotfix release is a type of incremental release that fixes specific issues.
+
+While OpenNebula is fully open source, packages from hotfix incremental versions are not publicly released, and are only available for users with an active commercial subscription. However, rest assured that the code is publicly available in the `GitHub repository <https://github.com/OpenNebula/one>`__, as is the `templates to create packages <https://github.com/OpenNebula/packages>`__ for the different supported platforms.
+
+Hence, everyone can create their own packages or :ref:`build OpenNebula from the source code <compile>`, but only OpenNebula Systems customers have the convenience of pre-created packages in Hotfixes incremental releases.
+
+if you are an OpenNebula Systems customer with an active support subscription you have access to the this hotfix package. Please check your private repository at OpenNebula.pro

source/operation/host_cluster_management/datastore_guide.rst

@@ -55,6 +55,8 @@ Also, there are a set of common attributes that can be used in any datastore and
 +------------------------------+----------------------------------------------------------------------------------------------------------------------------------+
 | ``DRIVER``                   | Specific image mapping driver enforcement. If present it overrides image ``DRIVER`` set in the image attributes and VM template. |
 +------------------------------+----------------------------------------------------------------------------------------------------------------------------------+
+| ``COMPATIBLE_SYS_DS``        | Only for IMAGE_DS. Specifies which system datastores are compatible with an image datastore by ID. Ex: "0,100"                   |
++------------------------------+----------------------------------------------------------------------------------------------------------------------------------+
 
 The Files & Kernels Datastore is an special datastore type to store plain files to be used as kernels, ram-disks or context files. :ref:`See here to learn how to define them <file_ds>`.
 

source/operation/vm_management/vm_instances.rst

@@ -213,7 +213,7 @@ Disk Snapshots
 
 There are two kinds of operations related to disk snapshots:
 
-* ``disk-snapshot-create``, ``disk-snapshot-revert``, ``disk-snapshot-delete``: Allows the user to take snapshots of the disk states and return to them during the VM life-cycle. It is also possible to delete snapshots.
+* ``disk-snapshot-create``, ``disk-snapshot-revert``, ``disk-snapshot-delete``, ``disk-snapshot-rename``: Allows the user to take snapshots of the disk states and return to them during the VM life-cycle. It is also possible to rename or delete snapshots.
 * ``disk-saveas``: Exports VM disk (or a previously created snapshot) to an image. This is a live action.
 
 .. warning:: Disk Snapshots are not supported in vCenter