Hi everyone,
I have seen problems caused by this behavior (always trying to download
public templates with URLs, and only migrating private templates and
public templates that do not have URLs) in some environments. For
instance, companies create temporary URLs to download templates from,
and delete them after the template gets downloaded; due to the existing
behavior, when a new image store is added and data is migrated to it,
ACS does not move the template to the new image store, and does not
download the template in the new image store either, forcing manual
intervention to move it. Also, suppose you download a template to an
image store from a URL. Some time passes, and the template in that URL
gets updated. Then, you add a new secondary storage that tries to
download the updated template from the same URL. After the download
finishes, ACS will compare the downloaded template's checksum with the
existing template's checksum, and fail to synchronize the template
because they differ. This way, you will also be forced to manually move
the template from the old image store to the new one.
Because of the aforementioned problems, I have been investigating the
development of an extension (such as some new configurations) that would
allow operators to migrate public templates with URLs (avoiding the
first issue) and to prioritize copying templates from existing image
stores instead of downloading them (avoiding both issues). I will keep
this thread updated as I make progress. Other opinions on this would
also be appreciated.
Best regards.
On 2024/04/25 08:51:05 Mevludin Blazevic wrote:
> Hi all,
>
> it looks like with every secondary storage migration Cloudstack tries to
> re-download all templates with URLs instead of simply grabbing the
> already downloaded template from the old image store. If that's true,
> how to avoid that behaviour?
>
> Mevludin
>
>
>
