Skip to content
Merged
Changes from 2 commits
Commits
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
30 changes: 27 additions & 3 deletions source/installguide/configuration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -1700,10 +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
fetching from their URLs, more details are as below.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
fetching from their URLs, more details are as below.
fetching from their URLs. More details below.



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

Choose a reason for hiding this comment

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

@harikrishna-patnala the table is not visible in the html.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

thanks @rajujith fixed it

image

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