M #-: Add callouts config file changes in maintenance releases

Signed-off-by: Pedro Ielpi <[email protected]>
pedroielpi3 · Feb 19, 2025 · b64808e · b64808e
1 parent e1bdeed
commit b64808e
Show file tree

Hide file tree

Showing 6 changed files with 31 additions and 7 deletions.
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``)