M #-: Modify technical details for new scheduler

Signed-off-by: Pedro Ielpi <[email protected]>

Author: pedroielpi3

source/installation_and_configuration/ha/frontend_ha.rst

@@ -316,7 +316,7 @@ The whole procedure is documented :ref:`above <frontend_ha_setup_add_remove_serv
 
 .. _frontend_ha_recover_servers:
 
-Recovering servers
+Recovering Servers
 ================================================================================
 
 When a *follower* is down for some time it may fall out of the recovery window, i.e. the log may not include all the records needed to bring it up to date. In order to recover this server you need to:
@@ -340,7 +340,7 @@ During maintenance you may use ``onezone disable zone_id``. Disabled zone can st
 
 .. _frontend_ha_shared:
 
-Shared data between HA nodes
+Shared data Between HA Nodes
 ================================================================================
 
 HA deployment requires the filesystem view of most datastores (by default in ``/var/lib/one/datastores/``) to be the same on all frontends. It is necessary to set up a shared filesystem over the datastore directories. This document doesn't cover configuration and deployment of the shared filesystem; it is left completely up to the cloud administrator.
@@ -386,7 +386,7 @@ The Raft algorithm can be tuned by several parameters in the configuration file
 
   Any change in these parameters can lead to unexpected behavior during the fail-over and result in whole-cluster malfunction. After any configuration change, always check the crash scenarios for the correct behavior.
 
-Compatibility with the earlier HA
+Compatibility with the Earlier HA
 =================================
 
 In OpenNebula <= 5.2, HA was configured using a classic active-passive approach, using Pacemaker and Corosync. While this still works for OpenNebula > 5.2, it is not the recommended way to set up a cluster. However, it is fine if you want to continue using that HA method if you're coming from earlier versions.
@@ -395,38 +395,30 @@ This is documented here: `Front-end HA Setup <http://docs.opennebula.io/5.2/adva
 
 .. _server_sync_ha:
 
-Synchronize configuration files across servers
+Synchronize Configuration Files Across Servers
 ================================================================================
 
-You can use the command ``onezone serversync``. This command is designed to help administrators to sync OpenNebula's configurations across High Availability (HA) nodes and fix lagging nodes in HA environments. It will first check for inconsistencies between local and remote configuration files inside ``/etc/one/`` directory. In case these exist, the local version will be replaced by the remote version and only the affected service will be restarted. Whole configuration files will be replaced with the sole exception of ``/etc/one/oned.conf``. In this case, the local ``FEDERATION`` configuration will be maintained, but the rest of the content will be overwritten. A backup will be made inside ``/etc/one/`` before replacing any file.
+To synchronize files, you can use the command ``onezone serversync``. This command is designed to help administrators to sync OpenNebula’s configurations across HA nodes and fix lagging nodes in HA environments. The command first checks for inconsistencies between local and remote configuration files inside the ``/etc/one/`` directory. If inconsistencies are found, the local version of a file will be replaced by the remote version, and only the affected service will be restarted. Whole configuration files will be replaced, with the sole exception of ``/etc/one/oned.conf``. For this file, the local ``FEDERATION`` configuration will be maintained, but the rest of the content will be overwritten. Before replacing any file, a backup will be made inside ``/etc/one/``.
 
-.. warning:: Only use this option between HA nodes, never across federated nodes
+.. warning:: Only use this option between HA nodes, never across federated nodes.
 
 This is the list of files that will be checked and replaced:
 
 Individual files:
 
-- ``/etc/one/az_driver.conf``
-- ``/etc/one/az_driver.default``
-- ``/etc/one/ec2_driver.conf``
-- ``/etc/one/ec2_driver.default``
-- ``/etc/one/econe.conf``
 - ``/etc/one/monitord.conf``
 - ``/etc/one/oneflow-server.conf``
 - ``/etc/one/onegate-server.conf``
-- ``/etc/one/vcenter_driver.default``
-
-
 
 Folders:
 
 - ``/etc/one/fireedge``
 - ``/etc/one/auth``
-- ``/etc/one/ec2query_templates``
 - ``/etc/one/hm``
+- ``/etc/one/schedulers``
 - ``/etc/one/vmm_exec``
 
-.. note:: Any file inside previous folders that doesn't exist on the remote server (like backups) will **not** be removed.
+.. note:: Any file inside the above folders that does not exist on the remote server (such as backups) will *not* be removed.
 
 Usage
 -----

source/integration_and_development/references/compile.rst

@@ -25,7 +25,7 @@ Follow these simple steps to install the OpenNebula software:
 
 .. note::
 
-    scons can parallelize the build with the `-j NUM_THREADS` parameter. For instance, to compile the with 4 parallel processes execute
+    scons can parallelize the build with the `-j NUM_THREADS` parameter. For instance, to compile the with 4 parallel processes execute:
 
     .. code::
 
@@ -145,29 +145,6 @@ The packages do a ``system-wide`` installation. To create a similar environment,
     scons: done building targets.
     oneadmin@frontend:~/opennebula-x.y.z $> sudo ./install.sh -u oneadmin -g oneadmin
 
-.. warning::
-
-   An error as below might occur during building process:
-    .. prompt:: bash # auto
-
-        # scons -j2 mysql=yes syslog=yes
-        /usr/bin/ld: src/common/libnebula_common.a(HttpRequest.o): undefined reference to symbol 'curl_easy_cleanup'
-        /usr/bin/ld: /usr/lib64/libcurl.so.4: error adding symbols: DSO missing from command line
-        collect2: error: ld returned 1 exit status
-        scons: *** [src/scheduler/src/sched/mm_sched] Error 1
-        scons: building terminated because of errors.
-
-    In that case one needs to patch ``src/scheduler/src/sched/SConstruct`` file:
-
-    .. prompt:: bash # auto
-
-       # diff one/src/scheduler/src/sched/SConstruct one-orig/src/scheduler/src/sched/SConstruct
-       48c48,49
-       <     'xml2'
-       ---
-       >     'xml2',
-       >     'curl'
-
 Ruby Dependencies
 ================================================================================
 

source/open_cluster_deployment/kvm_node/kvm_driver.rst

@@ -481,10 +481,10 @@ Tuning & Extending
 
 .. _kvm_multiple_actions:
 
-Multiple Actions per Host
+Multiple Actions per Host or Cluster
 --------------------------------------------------------------------------------
 
-By default the VMM driver is configured to allow more than one action to be executed per Host. Make sure the parameter ``-p`` is added to the driver executable. This is done in ``/etc/one/oned.conf`` in the VM_MAD configuration section:
+By default the VMM driver is configured to allow more than one action to be executed per Host. Make sure the parameter ``-p`` is added to the driver executable. This is done in ``/etc/one/oned.conf``, in the ``VM_MAD`` configuration section:
 
 .. code::
 
@@ -495,23 +495,27 @@ By default the VMM driver is configured to allow more than one action to be exec
         DEFAULT    = "vmm_exec/vmm_exec_kvm.conf",
         TYPE       = "kvm" ]
 
-Restart the main OpenNebula service if changes were made to the mentioned file:
+Additionally, also in ``/etc/one/oned.conf``, increase the value of the ``MAX_ACTIONS_PER_HOST`` (default = ``1``), for example:
+
+.. prompt:: bash $ auto
+
+  MAX_ACTIONS_PER_HOST = 10
+
+To increase the maximum number of allowed actions per cluster, increase the value of the ``MAX_ACTIONS_PER_CLUSTER`` parameter (default = ``30``).
+
+After changing ``/etc/one/oned.conf``, restart the main OpenNebula service:
 
 .. prompt:: bash $ auto
 
     $ sudo systemctl restart opennebula
 
-The scheduler configuration should be changed to let it deploy more than one VM per Host. The file is located at ``/etc/one/sched.conf`` and the value to change is ``MAX_HOST`` For example, to let the scheduler submit 10 VMs per Host use this line:
+Additionally, if you are using the Rank Scheduler, you will need to change the configuration to let the scheduler deploy more than one VM per Host. In the file ``/etc/one/schedulers/rank.conf``, change the value of the ``MAX_HOST`` parameter. For example, to let the scheduler submit 10 VMs per Host:
 
 .. code::
 
     MAX_HOST = 10
 
-Restart the scheduler service for this change to take effect:
-
-.. prompt:: bash $ auto
-
-    $ sudo systemctl restart opennebula-scheduler
+Changes in ``rank.conf`` do not require a restart.
 
 .. _kvmg_files_and_parameters: