Merge branch 'main' into update-text-and-images-for-Installation-Guide-of-VMWare-to-7.0.3

Author: daviftorres

source/adminguide/hosts.rst

@@ -246,7 +246,7 @@ devices on a KVM host. The script is located in the
 ``/usr/share/cloudstack-common/scripts/vm/`` directory on the host. The script
 relies on the ``lspci`` & ``xmlstarlet`` command to discover the GPU devices
 and their status on the host. So, for the discovery to be successful, the
-``lspci`` & ``xmlstarlet`` commands needs to be installed on the host.
+``lspci`` & ``xmlstarlet`` should be installed on the host.
 
    .. parsed-literal::
 
@@ -266,7 +266,7 @@ and their status on the host. So, for the discovery to be successful, the
    ===============================   ==================   =======================
    Legacy: SR-IOV not supported      `mdev`                 Yes
    SR-IOV supported                  `mdev`                 Yes
-   SR-IOV supported                  `Vendor specific`      No
+   SR-IOV supported                  `Vendor specific`      Yes
    Multi Instance GPU                                       No
    ===============================   ==================   =======================
 

source/adminguide/service_offerings.rst

@@ -306,7 +306,9 @@ To create a new compute offering:
    -  **GPU Display**: Whether to use the GPU device attached to the guest instance for display.
       This is applicable only for KVM hypervisor. Depending on the OS and display configuration,
       the user might need to set ``video.hardware`` to ``none`` in the instance's settings to
-      use CPVM for display.
+      use CPVM for display. To set the ``video.hardware`` setting, navigate to
+      the instance's details page in the CloudStack UI, click on the
+      "Settings" tab, and add/or update the ``video.hardware`` setting to ``none``.
 
    -  **Public**: Indicate whether the compute offering should be
       available to all domains or only some domains. Choose Yes to make it

source/installguide/hypervisor/kvm.rst

@@ -165,6 +165,19 @@ KVM Instances.
    is the selected/active one (in case you had a previous Java version already installed)
    with ``alternatives --config java``, after CloudStack agent is installed.
 
+.. note::
+   SUSE Linux Enterprise Server 15 (SP7) requires the following steps to install Java 17 and prepare the host.
+
+.. parsed-literal::
+
+   SUSEConnect --product sle-module-legacy/15.7/x86_64
+   zypper install java-17-openjdk-17.0.15.0-150400.3.54.1
+   SUSEConnect --product PackageHub/15.7/x86_64
+   zypper install rng-tools
+   wget https://download.opensuse.org/repositories/openSUSE:/Leap:/15.2/standard/noarch/timezone-java-2020a-lp152.2.1.noarch.rpm
+   rpm -ivh timezone-java-2020a-lp152.2.1.noarch.rpm
+
+
 Configure package repository
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -229,7 +242,7 @@ information.
 
    [cloudstack]
    name=cloudstack
-   baseurl=http://download.cloudstack.org/suse/|version|/
+   baseurl=http://download.cloudstack.org/suse/$releasever/|version|/
    enabled=1
    gpgcheck=0
 
@@ -298,6 +311,11 @@ In SUSE:
 
    $ zypper install cloudstack-agent
 
+SUSE Linux Enterprise Server 15 (SP7) requires the following entry to be made in the /etc/cloudstack/agent/agent.properties file; the clock speed can be set to match the host CPU. 
+
+.. parsed-literal::
+
+   host.cpu.manual.speed.mhz=2350 
 
 The host is now ready to be added to a cluster. This is covered in a
 later section, see :ref:`adding-a-host`. It is
@@ -472,7 +490,7 @@ cloudstack-agent and should already be installed.
 
       #LIBVIRTD_ARGS="--listen"
 
-   Configure libvirt to connect to libvirtd and not to per-driver daemons, especially important on newer distros such as EL9 and Ubuntu 24.04. 
+   Configure libvirt to connect to libvirtd and not to per-driver daemons, especially important on newer distros such as EL9, SUSE 15 SP7 and Ubuntu 24.04. 
    Edit ``/etc/libvirt/libvirt.conf`` and add the following:
 
    .. parsed-literal::

source/installguide/optional_installation.rst

@@ -114,6 +114,39 @@ For storing certificates, admins can create and configure a java keystore file
 and configure the same in the server.properties file as illustrated above.
 
 
+Health Checks and Monitoring (Optional)
+---------------------------------------
+
+CloudStack has a plugin for exporting metrics in the format that Prometheus can consume.
+This is done by enabling the following configuration parameters in the Global Settings.
+
+   .. parsed-literal::
+
+      # cloudmonkey update configuration name=prometheus.exporter.enable      value=true
+      # cloudmonkey update configuration name=prometheus.exporter.port        value=9595
+      # cloudmonkey update configuration name=prometheus.exporter.allowed.ips value="127.0.0.1,192.168.0.10"
+
+.. note:: 
+   These settings are available to be configured via the CloudStack UI as well.
+   CloudStack Management needs to be restarted for the changes to take effect.
+   Replace the mock IP address 192.168.0.10 with the actual IP address of the Prometheus server.
+
+.. warning::
+   A list of addresses can be provided as a comma separated list. It does NOT accept CIDR notation.
+
+Then, configure prometheus to start pulling metrics by adding the following configuration to ``/etc/prometheus/prometheus.yml``.
+
+   .. parsed-literal::
+
+      - job_name: 'management'
+         static_configs:
+            - targets: ['192.168.0.20:9595']
+
+.. note::
+   Replace the mock IP address 192.168.0.20 with the actual IP address of the Management server.
+   Public dashboards are available in the Grafana repository for visualizing CloudStack Management metrics.
+
+
 Database Replication (Optional)
 -------------------------------