Merge branch 'main' of https://github.com/apache/cloudstack-documentation into netris-integration

Author: Pearl1594

source/_static/images/cks-cni-configuration-cluster-creation.png

@@ -45,6 +45,10 @@ the default username is password.
 
 Domain -> If you are a root User, leave this field blank.
 
+.. note::
+
+   Since 4.21 it is possible to login to a specific Project view by enabling the 'displayProjectFieldOnLogin' setting on config.json (which is disabled by default). Please refer to: :ref:`enable-login-to-project-view`.
+
 If you are a User in the sub-domains, enter the full path to the domain,
 excluding the root domain.
 
@@ -508,7 +512,64 @@ For displaying a custom HTML in the plugin, HTML file can be stored in the Cloud
 |ui-custom-plugin.png|
 
 
-Instance Image Selction Customisation
+Announcement Banner
+===================
+
+Admin can configure an **announcement banner** in `config.json` to display alerts or messages to all users. 
+This banner is useful for communicating important notices such as performance issues, scheduled maintenance, or general announcements.
+To enable and customize the banner, use the `announcementBanner` section in the config.json file. 
+
+This section supports the following properties:
+
+**Configuration Example**
+
+.. parsed-literal::
+
+  "announcementBanner": {
+    "enabled": true,
+    "showIcon": true,
+    "closable": true,
+    "persistDismissal": true,
+    "type": "warning",
+    "message": "<strong>Performance Notice:</strong> We're experiencing high load. Some operations may be slower than usual.",
+    "startDate": "2025-06-01T00:00:00Z",
+    "endDate": "2025-07-16T00:00:00Z"
+   }
+
+**Banner Display Example**
+
+Based on the configuration above, the following banner is shown in the user interface:
+
+.. image:: /_static/images/ui-announcement-banner.png
+   :align: center
+   :alt: UI Announcement banner
+
+--------
+
+**Properties Description**
+
+- **enabled**: Enables or disables the announcement banner (`true` or `false`).
+- **showIcon**: Displays an icon alongside the message. The icon corresponds to the banner `type`.
+- **closable**: Allows users to close the banner.
+- **persistDismissal**: Remembers the user's dismissal of the banner, so it doesn't reappear.
+- **type**: Specifies the type of banner. Supported values are:
+  
+  - `info`
+  - `warning`
+  - `error`
+  - `success`
+
+- **message**: The HTML-formatted content displayed in the banner.
+- **startDate** / **endDate**: Define the visibility window for the banner using ISO 8601 format (`YYYY-MM-DDTHH:MM:SSZ`).
+
+.. note::
+
+   - The `message` property supports basic HTML, allowing styled content such as `<strong>` tags for emphasis.
+   - Banner's background color changes based on `type` property value. White color is used for banner if `type` is not defined or has invalid value.
+   - Multi-line message is supported, however recommendation is to limit it to 2 lines. Content may overlap banner for more than 2 lines.
+
+
+Instance Image Selection Customisation
 -------------------------------------
 
 In the UI, there are several forms where the user needs to select an image (template/ISO) for an instance, such as deploying an instance, reinstalling an instance, creating a VNF appliance, etc. The image selection interface for these forms can be selected by the operator based on preference by specifying properties in the UI configuration file (config.json).
@@ -523,6 +584,7 @@ The *legacy* interface will display images based on templatefilter/isofilter, i.
 
 |ui-legacy-image-selection.png|
 
+
 Advanced UI Customisation
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -602,6 +664,23 @@ For the UI to work with different servers, it is necessary to configure the Ngin
 
 |ui-multiple-server-management.png|
 
+.. _enable-login-to-project-view:
+
+Enable Login to Project View
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+User can use the file /etc/cloudstack/management/config.json to enable the Project field displayed on Login by the setting:
+
+============================= =================================================================
+Property                      Description
+============================= =================================================================
+displayProjectFieldOnLogin    Disabled by default. When enabled, login directly to Project view
+============================= =================================================================
+
+When the Project field is set and the Project exists, the user is directly directed to the Project view instead of the Default View.
+
+|ui-login-project-view.png|
+
 Known Limitations
 ~~~~~~~~~~~~~~~~~
 
@@ -626,3 +705,6 @@ The following features are no longer supported or available in the UI but are st
 
 .. |ui-multiple-server-management.png| image:: /_static/images/ui-multiple-server-management.png
    :alt: Custom plugin shown in UI with navigation
+
+.. |ui-login-project-view.png| image:: /_static/images/ui-login-project-view.png
+   :alt: Enabling the Project field on login

source/_static/images/cks-cni-configuration-registration-sample.png

@@ -77,4 +77,63 @@ firstfitleastconsumed          Selects the first storage pool after sorting elig
 
       **volume.allocation.algorithm**: random (default)
 
-   Before 4.21.0, **vm.allocation.algorithm** was used for both VM as well as Volume allocation.
+   Before 4.21.0, **vm.allocation.algorithm** was used for both VM as well as Volume allocation.
+
+
+Cluster, Pod and Host Ordering
+==============================
+
+Overview
+--------
+
+`The host.capacityType.to.order.clusters` is a global advanced configuration parameter in Apache CloudStack that controls how pods, clusters, 
+and hosts are prioritized during Instance deployment, based on available CPU, RAM, or a weighted combination of both in Host.
+This configuration is specifically leveraged when the VM allocation algorithm is set to `firstfitleastconsumed`.
+
+Configuration
+-------------
+
+Key: `host.capacityType.to.order.clusters`
+
+.. cssclass:: table-striped table-bordered table-hover
+
+========= ========================
+Value      Behavior
+========= ========================
+CPU		  Prioritizes resources with the most available CPU.
+RAM		  Prioritizes resources with the most available memory.
+COMBINED	  Uses a weighted formula to balance CPU and RAM in prioritization.
+========= ========================
+
+**Additional Configuration for COMBINED**
+
+- Key: `host.capacityType.to.order.clusters.cputomemoryweight`
+- Type: Float(0.0 to 1.0)
+- Default: 0.5
+- Purpose: Determines the weight of CPU vs RAM in the combined capacity calculation.
+
+Capacity calculation formula:
+
+.. code:: bash
+
+   capacity = (host.capacityType.to.order.clusters.cputomemoryweight * CPU) + ((1 - host.capacityType.to.order.clusters.cputomemoryweight) * RAM)
+
+
+This allows flexible tuning of prioritization depending on workload sensitivity.
+
+Example Configuration
+---------------------
+
+.. code:: bash
+
+   host.capacityType.to.order.clusters: COMBINED
+   host.capacityType.to.order.clusters.cputomemoryweight: 0.7
+
+Above config prioritizes CPU at 70% weight and RAM at 30% when ranking pods, clusters, and hosts.
+
+.. note::
+   - `host.capacityType.to.order.clusters` is only respected for host ordering when:
+   .. code:: bash
+
+      vm.allocation.algorithm: firstfitleastconsumed
+   - When using COMBINED, make sure to tune cpu.to.memory.capacity.weight to reflect your environment’s resource constraints and workload profiles.