Thanks Andrija, will try to work with the solution proposed.
Ran
On 11/22/2018 02:25 PM, Andrija Panic wrote:
I confirm bug...tmpl not removed...
And I confirm a possible solution:
"volumes" table, field "template_id" should be set to NULL for this
particular volume, after volume restored f
I confirm bug...tmpl not removed...
And I confirm a possible solution:
"volumes" table, field "template_id" should be set to NULL for this
particular volume, after volume restored from snapshot - on next storage
scavenger run it will be marked properly for GC and removed...
(volumes of VM deploy
Hi Andrija,
That is precisely the step I went through.
However the template was not cleaned up after expected interval when no
other volume have it as a backing image.
regards,
Ran
On 11/22/2018 12:53 PM, Andrija Panic wrote:
Hi Run,
not sure what you mean (I did not quite understand your
Looks like a bug (missing processing case).
чт, 22 нояб. 2018 г., 15:54 Andrija Panic andrija.pa...@gmail.com:
> Hi Run,
>
> not sure what you mean (I did not quite understand your explanation) - but
> here is an exercise from my side (just done it):
>
> https://pasteboard.co/HOowNao.png
>
> Che
Hi Run,
not sure what you mean (I did not quite understand your explanation) - but
here is an exercise from my side (just done it):
https://pasteboard.co/HOowNao.png
Check the image - explanation below:
Centos55 minimal (builtin) template, spin new VM:
--- new volume created with UUID/PATH (n
Thanks Andrija, just tested myself with expunge and works as expected.
However, for KVM, when I revert a qcow disk from snapshot, which removes
the backing chain to template, the template will not be removed.
So it seems like despite the qcow disk is no longer backed by the
template, the temp
new template, deployed new VM, destroyed VM (with Exunge option)...
up to 120sec later... (storage.cleanup.interval=120 sec, global config
option)
2018-11-19 19:35:59,525 DEBUGStorage pool garbage collector found 1
templates to clean up in storage pool: Primary-storage - NFS
2018-11-19 19:35:59,
True (at least I'm sure for SolidFire) - but I believe in general also
(will test this now...)
On Mon, 19 Nov 2018 at 18:51, Dag Sonstebo
wrote:
> Developers please correct me... but as far as I remember there is a
> garbage collector which does remove the templates from primary storage once
> t
Developers please correct me... but as far as I remember there is a garbage
collector which does remove the templates from primary storage once they are
not needed (i.e. have no more "child VMs"). This is controlled by the global
setting "storage.template.cleanup.enabled".
Regards,
Dag Sonstebo
Hi Andrija,
Thanks for the clarification and quick response
regards,
Ran
On 11/16/2018 02:15 PM, Andrija Panic wrote:
Hi Ran,
templates stays on Primary Storage "forever", at least for NFS (they are
moved from Secondary to Primary when you deploy a very first VM from
specific template). All V
Hi Ran,
templates stays on Primary Storage "forever", at least for NFS (they are
moved from Secondary to Primary when you deploy a very first VM from
specific template). All VMs have this templates qcow2 as baking (parent)
image.
This template is a qcow2 copy of a file from Secondary Storage - an
11 matches
Mail list logo
