From 822838ba314b1cfc4e116b539f0e55f6f23746a4 Mon Sep 17 00:00:00 2001 From: Harikrishna Patnala Date: Thu, 18 Dec 2025 18:14:16 +0530 Subject: [PATCH 1/4] Improvements added in making the existing templates available on newly added secondary storage --- source/installguide/configuration.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/source/installguide/configuration.rst b/source/installguide/configuration.rst index 5d1a3e878e..4aa0c30b2b 100644 --- a/source/installguide/configuration.rst +++ b/source/installguide/configuration.rst @@ -1705,6 +1705,26 @@ add more servers to an existing zone. - Path. The path to the zone's Secondary Staging Store. +When a new Secondary Storage is added, the Management Server attempts to make +existing templates available on the new Secondary Storage. + +CloudStack improves template availability using the configuration: + ++----------------------------------------------+-------------------------------------------------------------------------------------------------------------+-----------+ +| Name | Description | Default | ++==============================================+=============================================================================================================+===========+ +| copy.templates.from.other.secondary.storages | Allow templates to be copied from existing Secondary Storage servers (within the same zone or across zones) | true | +| | when adding a new Secondary Storage, instead of downloading them from the source URL. | | ++----------------------------------------------+-------------------------------------------------------------------------------------------------------------+-----------+ + +This setting is enabled by default and can be configured globally or at zone level. + +CloudStack applies the following order of steps while trying to make a template available in the new secondary storage: + +1. Attempt to copy the template from another Secondary Storage in the same zone. +2. If not found, attempt to copy the template from a Secondary Storage in a different zone. +3. If the copy operation fails, CloudStack falls back to downloading the template using its URL when it is registered. + Adding an NFS Secondary Staging Store for Each Zone ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From adc272ae6b03477fc810cb81d6bebad79473ee63 Mon Sep 17 00:00:00 2001 From: Harikrishna Patnala Date: Mon, 29 Dec 2025 14:52:55 +0530 Subject: [PATCH 2/4] Added parameter details --- source/installguide/configuration.rst | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/source/installguide/configuration.rst b/source/installguide/configuration.rst index 4aa0c30b2b..05b7bbc9c1 100644 --- a/source/installguide/configuration.rst +++ b/source/installguide/configuration.rst @@ -1686,7 +1686,7 @@ add more servers to an existing zone. Swift or S3 is used as the secondary storage provider, an NFS staging storage in each zone is still required. - - Zone. The zone where the NFS Secondary Staging Store is to be + - Zone: The zone where the NFS Secondary Staging Store is to be located. - **SMB Username**: Applicable only if you select SMB/CIFS provider. @@ -1700,9 +1700,13 @@ add more servers to an existing zone. - **SMB Domain**: Applicable only if you select SMB/CIFS provider. The Active Directory domain that the SMB share is a part of. - - NFS server. The name of the zone's Secondary Staging Store. + - NFS server: The name of the zone's Secondary Staging Store. - - Path. The path to the zone's Secondary Staging Store. + - Path: The path to the zone's Secondary Staging Store. + + - Copy templates from other storages: This switch can be used to automatically + copy existing templates from secondary storages in other zones instead of + fetching from their URLs, more details are as below. When a new Secondary Storage is added, the Management Server attempts to make From c4e9ba61ee0ea4566a987b0ba61d718d67d530d3 Mon Sep 17 00:00:00 2001 From: Harikrishna Patnala Date: Mon, 29 Dec 2025 15:29:00 +0530 Subject: [PATCH 3/4] corrections --- source/installguide/configuration.rst | 32 +++++++++++++-------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/source/installguide/configuration.rst b/source/installguide/configuration.rst index 05b7bbc9c1..9b458660ac 100644 --- a/source/installguide/configuration.rst +++ b/source/installguide/configuration.rst @@ -1664,9 +1664,9 @@ add more servers to an existing zone. #. Fill in the following fields: - - Name. Give the storage a descriptive name. + - **Name**: Give the storage a descriptive name. - - Provider. Choose S3, Swift, NFS, or CIFS then fill in the related + - **Provider**: Choose S3, Swift, NFS, or CIFS then fill in the related fields which appear. The fields will vary depending on the storage provider; for more information, consult the provider's documentation (such as the S3 or Swift website). NFS can be used @@ -1677,7 +1677,7 @@ add more servers to an existing zone. Heterogeneous Secondary Storage is not supported in Regions. You can use only a single NFS, S3, or Swift account per region. - - Create NFS Secondary Staging Store. This box must always be + - **Create NFS Secondary Staging Store**: This box must always be checked. .. warning:: @@ -1686,7 +1686,7 @@ add more servers to an existing zone. Swift or S3 is used as the secondary storage provider, an NFS staging storage in each zone is still required. - - Zone: The zone where the NFS Secondary Staging Store is to be + - **Zone**: The zone where the NFS Secondary Staging Store is to be located. - **SMB Username**: Applicable only if you select SMB/CIFS provider. @@ -1700,34 +1700,34 @@ add more servers to an existing zone. - **SMB Domain**: Applicable only if you select SMB/CIFS provider. The Active Directory domain that the SMB share is a part of. - - NFS server: The name of the zone's Secondary Staging Store. + - **NFS server**: The name of the zone's Secondary Staging Store. - - Path: The path to the zone's Secondary Staging Store. + - **Path**: The path to the zone's Secondary Staging Store. - - Copy templates from other storages: This switch can be used to automatically - copy existing templates from secondary storages in other zones instead of + - **Copy Templates from other storages**: This switch can be used to automatically + copy existing Templates from Secondary Storages in other Zones instead of fetching from their URLs, more details are as below. When a new Secondary Storage is added, the Management Server attempts to make -existing templates available on the new Secondary Storage. +existing Templates available on the new Secondary Storage. -CloudStack improves template availability using the configuration: +CloudStack improves Template availability using the configuration: +----------------------------------------------+-------------------------------------------------------------------------------------------------------------+-----------+ | Name | Description | Default | +==============================================+=============================================================================================================+===========+ -| copy.templates.from.other.secondary.storages | Allow templates to be copied from existing Secondary Storage servers (within the same zone or across zones) | true | +| copy.templates.from.other.secondary.storages | Allow templates to be copied from existing Secondary Storages (within the same Zone or across Zones) | true | | | when adding a new Secondary Storage, instead of downloading them from the source URL. | | +----------------------------------------------+-------------------------------------------------------------------------------------------------------------+-----------+ -This setting is enabled by default and can be configured globally or at zone level. +This setting is enabled by default and can be configured globally or at Zone level. -CloudStack applies the following order of steps while trying to make a template available in the new secondary storage: +CloudStack applies the following order of steps while trying to make a Template available in the new Secondary Storage: -1. Attempt to copy the template from another Secondary Storage in the same zone. -2. If not found, attempt to copy the template from a Secondary Storage in a different zone. -3. If the copy operation fails, CloudStack falls back to downloading the template using its URL when it is registered. +1. Attempt to copy the Template from another Secondary Storage in the same Zone. +2. If not found, attempt to copy the Template from a Secondary Storage in a different Zone. +3. If the copy operation fails, CloudStack falls back to downloading the Template using its URL when it is registered. Adding an NFS Secondary Staging Store for Each Zone ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From 423da79d11fb5c2f3ddfa0eb376791b3754499d2 Mon Sep 17 00:00:00 2001 From: Harikrishna Patnala Date: Mon, 29 Dec 2025 15:35:00 +0530 Subject: [PATCH 4/4] more corrections --- source/installguide/configuration.rst | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/source/installguide/configuration.rst b/source/installguide/configuration.rst index 9b458660ac..d8d945d802 100644 --- a/source/installguide/configuration.rst +++ b/source/installguide/configuration.rst @@ -1635,9 +1635,9 @@ System Requirements for Secondary Storage Adding Secondary Storage ~~~~~~~~~~~~~~~~~~~~~~~~ -When you create a new zone, the first secondary storage is added as part -of that procedure. You can add secondary storage servers at any time to -add more servers to an existing zone. +When you create a new Zone, the first Secondary Storage is added as part +of that procedure. You can add Secondary Storage servers at any time to +add more servers to an existing Zone. .. warning:: Ensure that nothing is stored on the server. Adding the server to @@ -1670,7 +1670,7 @@ add more servers to an existing zone. fields which appear. The fields will vary depending on the storage provider; for more information, consult the provider's documentation (such as the S3 or Swift website). NFS can be used - for zone-based storage, and the others for region-wide storage. + for Zone-based storage, and the others for region-wide storage. For Hyper-V, select SMB/CIFS. .. warning:: @@ -1683,10 +1683,10 @@ add more servers to an existing zone. .. warning:: Even if the UI allows you to uncheck this box, do not do so. This checkbox and the three fields below it must be filled in. Even when - Swift or S3 is used as the secondary storage provider, an NFS staging + Swift or S3 is used as the Secondary Storage provider, an NFS staging storage in each zone is still required. - - **Zone**: The zone where the NFS Secondary Staging Store is to be + - **Zone**: The Zone where the NFS Secondary Staging Store is to be located. - **SMB Username**: Applicable only if you select SMB/CIFS provider. @@ -1700,9 +1700,9 @@ add more servers to an existing zone. - **SMB Domain**: Applicable only if you select SMB/CIFS provider. The Active Directory domain that the SMB share is a part of. - - **NFS server**: The name of the zone's Secondary Staging Store. + - **NFS server**: The name of the Zone's Secondary Staging Store. - - **Path**: The path to the zone's Secondary Staging Store. + - **Path**: The path to the Zone's Secondary Staging Store. - **Copy Templates from other storages**: This switch can be used to automatically copy existing Templates from Secondary Storages in other Zones instead of @@ -1717,7 +1717,7 @@ CloudStack improves Template availability using the configuration: +----------------------------------------------+-------------------------------------------------------------------------------------------------------------+-----------+ | Name | Description | Default | +==============================================+=============================================================================================================+===========+ -| copy.templates.from.other.secondary.storages | Allow templates to be copied from existing Secondary Storages (within the same Zone or across Zones) | true | +| copy.templates.from.other.secondary.storages | Allow Templates to be copied from existing Secondary Storages (within the same Zone or across Zones) | true | | | when adding a new Secondary Storage, instead of downloading them from the source URL. | | +----------------------------------------------+-------------------------------------------------------------------------------------------------------------+-----------+