Skip to content

Allow copy of templates from secondary storages of same or other zone when adding a new secondary storage #611

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
harikrishna-patnala wants to merge 1 commit into
base: 4.20
Choose a base branch
from
+20 −0
Open

Allow copy of templates from secondary storages of same or other zone when adding a new secondary storage #611

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions source/installguide/configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Contributor

@DaanHoogland DaanHoogland Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when creating a zone it is enabled by default, so preventing it will be hard right? A race against the machine.

Copy link
Contributor Author

@harikrishna-patnala harikrishna-patnala Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point Daan. When creating a zone, it uses the global setting (not zone level). I also want to keep the default value to false to keep it backward compatible. But the first PR is already merged apache/cloudstack#10363, I can do that change in my subsequent PR apache/cloudstack#12296

One another point to note, if the setting is enabled, first it attempts to copy from secondary storage, if it fails then it fall back to old behavior.


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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down