harikrishna-patnala commented on code in PR #611:
URL:
https://github.com/apache/cloudstack-documentation/pull/611#discussion_r2631182917
##########
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.
Review Comment:
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
https://github.com/apache/cloudstack/pull/10363, I can do that change in my
subsequent PR https://github.com/apache/cloudstack/pull/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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
