Changing the template and refreshing the cache works like a charm.
I noticed that as the new cached image is created the old one remains.
I scanned the whole database for the uuid as it is nowhere to be found
except in events when a new VM is created.

Is there a table or place where I can get the ID of the old cached image
and delete it? How does ACS track and locate cached images?

Regards,
Jordan





On Mon, Sep 26, 2022 at 3:38 PM jordan j <yordan...@gmail.com> wrote:

> Thank you! :)
>
> On Mon, Sep 26, 2022 at 3:08 PM Wei ZHOU <ustcweiz...@gmail.com> wrote:
>
>> Hi Jordan,
>>
>> As said, you can find the information of template cache on primary storage
>> in table  `template_spool_ref`  table in cloud database.
>> If you want to clear the template cache, just remove the corresponding
>> record from the database, cloudstack will copy the template from secondary
>> storage to primary storage.
>>
>> -Wei
>>
>> On Mon, 26 Sept 2022 at 13:44, jordan j <yordan...@gmail.com> wrote:
>>
>> > I don't have ssl keys so i cannot import it.
>> > Is there a better way to do it, I am all ears :)?
>> >
>> > Best regards,
>> > Jordan
>> >
>> >
>> >
>> > On Mon, Sep 26, 2022 at 12:10 PM Wei ZHOU <ustcweiz...@gmail.com>
>> wrote:
>> >
>> > > Hi Jordan,
>> > >
>> > > You may look at the `template_spool_ref` table in the `cloud`
>> database.
>> > >
>> > > btw: why not register the new template  ?
>> > >
>> > > -Wei
>> > >
>> > > On Mon, 26 Sept 2022 at 11:02, jordan j <yordan...@gmail.com> wrote:
>> > >
>> > > > Hey everyone,
>> > > >
>> > > > Looking for automated way to deploy VHD image as a template i have
>> done
>> > > > this:
>> > > > - create a dummy template from VM
>> > > > - change the dummy template VHD on the NFS with the VHD image i have
>> > > > prepared
>> > > >
>> > > > So far so good but as VMs are created, the template VHD is cached on
>> > the
>> > > > hypervisor.
>> > > >
>> > > > Now if the template VHD on the NFS is changed again and a new VM is
>> > > > launched on a hypervisor that has the image cached, the new VM will
>> not
>> > > be
>> > > > created from the updated VHD disk.
>> > > >
>> > > > I tried to delete the cached image on the hypervisor manually but
>> ACS
>> > > does
>> > > > not like that and instead of downloading the new image error about a
>> > > > missing vhd file is presented.
>> > > >
>> > > > Is there any way to make cloudstack intentionally refresh the
>> > hypervisor
>> > > > image cache?
>> > > >
>> > > > Regards,
>> > > > Jordan
>> > > >
>> > >
>> >
>>
>

Reply via email to