Merge branch '4.15' into new-ui

Author: davidjumani

source/adminguide/service_offerings.rst

@@ -188,7 +188,14 @@ To create a new compute offering:
       NFS.
 
    -  **Provisioning type**: The type of disk that should be allocated.
-      Local
+      Valid values are thin, sparse, fat. When using the VMWare hypervisor,
+      these values are mapped to the following vSphere disk provisioning types:
+
+      -  **thin**:  **Thin Provision**
+      -  **sparse**:  **Thick Provision Lazy Zeroed**
+      -  **fat**:   **Thick Provision Eager Zeroed**
+
+      The disk provisioning type strictness on VMWare is controlled with the zone level setting - **disk.provisioning.type.strictness**. If set to true, the disk is created only when there is a suitable storage pool that supports the disk provisioning type specified by the service/disk offering. If set to false, the disk is created with a disk provisioning type supported by the pool. Default value is false and this is currently supported for VMware only.
 
    -  **Compute Offering Type**: The amount of freedom that the end user
       has to customise the compute power that their instance has when using this
@@ -383,6 +390,16 @@ To create a new disk offering:
    -  **Disk Size**: Appears only if Custom Disk Size is not selected.
       Define the volume size in GB (2^30 1GB = 1,073,741,824 Bytes).
 
+   -  **Provisioning type**: The type of disk that should be allocated.
+      Valid values are thin, sparse, fat. When using the VMWare hypervisor,
+      these values are mapped to the following vSphere disk provisioning types:
+
+      -  **thin**:  **Thin Provision**
+      -  **sparse**:  **Thick Provision Lazy Zeroed**
+      -  **fat**:   **Thick Provision Eager Zeroed**
+
+      The disk provisioning type strictness on VMWare is controlled with the zone level setting - **disk.provisioning.type.strictness**. If set to true, the disk is created only when there is a suitable storage pool that supports the disk provisioning type specified by the service/disk offering. If set to false, the disk is created with a disk provisioning type supported by the pool. Default value is false and this is currently supported for VMware only.
+
    -  **QoS Type** [2]_: Three options: Empty (no Quality of Service), hypervisor
       (rate limiting enforced on the hypervisor side), and storage
       (guaranteed minimum and maximum IOPS enforced on the storage
@@ -704,4 +721,3 @@ default system offering used for System VMs.
 
 #. Destroy the existing CPVM or SSVM offerings and wait for them to be
    recreated. The new CPVM or SSVM are configured with the new offering.
-

source/installguide/building_from_source.rst

@@ -146,7 +146,9 @@ You will need, at a minimum, the following to compile CloudStack:
 
 #. Maven (version 3)
 
-#. Java (Java 8/OpenJDK 1.8)
+#. Java (Java 11/OpenJDK 1.11)
+
+#. NodeJS (LTS/12)
 
 #. Apache Web Services Common Utilities (ws-commons-util)
 
@@ -254,6 +256,8 @@ several other dependencies. Note that we recommend using Maven 3.
    $ sudo apt-get install python-software-properties
    $ sudo apt-get update
    $ sudo apt-get install debhelper openjdk-11-jdk libws-commons-util-java genisoimage libcommons-codec-java libcommons-httpclient-java liblog4j1.2-java maven
+   $ curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -
+   $ sudo apt-get install -y nodejs
 
 .. note::
 
@@ -414,6 +418,8 @@ Linux.
 .. parsed-literal::
 
    # yum install java-11-openjdk-devel genisoimage mysql mysql-server ws-commons-util MySQL-python python-setuptools createrepo
+   # curl -sL https://rpm.nodesource.com/setup_12.x | sudo bash -
+   # yum install nodejs
 
 Next, you'll need to install build-time dependencies for CloudStack with
 Maven. We're using Maven 3, so you'll want to grab `Maven 3.0.5 (Binary tar.gz)

source/installguide/hypervisor/kvm.rst

@@ -455,6 +455,12 @@ infrastructure.
 By default these bridges are called *cloudbr0* and *cloudbr1* etc, but this can be 
 changed to be more description. 
 
+.. note::
+   Ensure that the interfaces names to be used for configuring the bridges match one of the following patterns:
+   **'eth*', 'bond*', 'team*', 'vlan*', 'em*', 'p*p*', 'ens*', 'eno*', 'enp*', 'enx*'**.
+
+   Otherwise, the KVM agent will not be able to configure the bridges properly.
+
 .. warning::
    It is essential that you keep the configuration consistent across all of your hypervisors.
 

source/installguide/hypervisor/vsphere.rst

@@ -51,6 +51,17 @@ Software requirements:
    Apply All Necessary Hotfixes. The lack of up-do-date hotfixes can lead to 
    data corruption and lost VMs.
 
+.. note::
+
+   When using vSphere and vCenter versions 6.0 and 6.5 there is a limitation on
+   instance names with a sequence number between 99999 and 1000000. For example if you take
+   a snapshot of a VM, the expected filename will be different to what cloudstack expects.
+   It is advisable to set the sequence number to 1M to prevent issues by executing the
+   following script on your cloudstack database:
+
+   UPDATE cloud.sequence
+   SET value = 1000000
+   WHERE name = 'vm_instance_seq';
 
 Hardware requirements:
 ^^^^^^^^^^^^^^^^^^^^^^

source/releasenotes/compat.rst

@@ -23,8 +23,8 @@ This section lists the operating systems that are supported for running
 CloudStack Management Server.
 
 -  Ubuntu 16.04 LTS, 18.04 LTS, 20.04 LTS
--  CentOS versions 7.x, 8.x (note: CentOS 8 will EOL in Dec 2021)
--  RHEL versions 7.x, 8.x
+-  CentOS versions 7, 8 (note: CentOS 8 will EOL in Dec 2021)
+-  RHEL versions 7, 8
 
 Software Requirements
 ~~~~~~~~~~~~~~~~~~~~~
@@ -39,8 +39,8 @@ CloudStack supports three hypervisor families, XenServer with XAPI, KVM,
 and VMware with vSphere.
 
 -  Ubuntu 16.04 LTS, 18.04, 20.04 LTS with KVM
--  CentOS 7.x, 8.x with KVM (note: CentOS 8 will EOL in Dec 2021)
--  Red Hat Enterprise Linux 7.x, 8.x with KVM
+-  CentOS 7, 8 with KVM (note: CentOS 8 will EOL in Dec 2021)
+-  Red Hat Enterprise Linux 7, 8 with KVM
 -  XenServer versions 7.0, 7.1, 7.2, 7.4, 7.5, 8.0 with latest hotfixes, XCP-ng 7.4, 7.6, 8.0, 8.1
 
    .. note:: It is now required to enable HA on the XenServer pool in order to recover from a pool-master failure. Please refer to the `XenServer documentation <https://docs.citrix.com/en-us/xencenter/7-1/pools-ha-enable.html>`_.