Skip to content

Conversation

@harikrishna-patnala
Copy link
Contributor

@harikrishna-patnala harikrishna-patnala commented Dec 18, 2025

This document is in relation to the PRs apache/cloudstack#10363 and apache/cloudstack#12296


📚 Documentation preview 📚: https://cloudstack-documentation--611.org.readthedocs.build/en/611/

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

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

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.

Copy link
Contributor

Choose a reason for hiding this comment

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

I do not mind enabling by default, just something to be aware of (and maybe document here). If useful to alternate we may wat to add a switch to the zone wizard (i.e set it before enabling the zone)

@abh1sar
Copy link
Contributor

abh1sar commented Dec 29, 2025

@blueorangutan docbuild

@blueorangutan
Copy link

@abh1sar a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress.

@blueorangutan
Copy link

QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/611. (QA-JID 470)

Copy link
Contributor

@abh1sar abh1sar left a comment

Choose a reason for hiding this comment

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

LGTM.

some nitpicks regarding capitalisations.

- 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 link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Copy templates from other storages: This switch can be used to automatically
- **Copy Templates from other storages**: This switch can be used to automatically

Could you also put the other fields in bold (if not already)

- 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 link
Contributor

Choose a reason for hiding this comment

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

Suggested change
copy existing templates from secondary storages in other zones instead of
copy existing Templates from Secondary Storages in other Zones instead of



When a new Secondary Storage is added, the Management Server attempts to make
existing templates available on the new Secondary Storage.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
existing templates available on the new Secondary Storage.
existing Templates available on the new Secondary Storage.

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:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
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 link
Contributor

Choose a reason for hiding this comment

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

Suggested change
| 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 Storage servers (within the same zone or across zones) | true |


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.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
3. If the copy operation fails, CloudStack falls back to downloading the template using its URL when it is registered.
3. If the copy operation fails, CloudStack falls back to downloading the Template using its URL when it is registered.

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
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Zone: The zone where the NFS Secondary Staging Store is to be
- **Zone**: The Zone where the NFS Secondary Staging Store is to be.


#. Fill in the following fields:

- Name. Give the storage a descriptive name.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- **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
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- **Provider**: Choose S3, Swift, NFS, or CIFS then fill in the related

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
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- **Create NFS Secondary Staging Store**: This box must always be

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants