[pve-devel] Adding creation time as metadata field to VM/containers?

[Victor Hooi]

Hi,

I'd still love the ability to query creation time for a VM - did you have
any more info on Dominik's metadata field you mentioned?

How difficult would this be to add?

Thanks,
Victor




Thanks,
Victor

On Tue, Jun 16, 2020 at 8:45 PM Victor Hooi <victorhooi at yahoo.com> wrote:

> Hi,
>
> In our case, we have users clone templates via the Proxmox Web UI - so I
> don't think setting the description field automatically there is an option.
> (As in, not sure how you'd hook it into the Web UI - or is there another
> way to have hooks/triggers for VMs created via the Web UI).
>
> What is Dominik's tags you're referring to? This seems interesting, and
> maybe this request could be lumped in there.
>
> Thanks,
> Victor
>
> On Wed, Jun 10, 2020 at 4:47 PM Thomas Lamprecht <t.lamprecht at proxmox.com>
> wrote:
>
>> Hi,
>>
>> On 6/9/20 11:13 PM, Victor Hooi wrote:
>> > Hi,
>> >
>> > Is there any chance of adding creation time as a queryable metadata
>> field
>> > for VMs/containers?
>> >
>> > The use-case for us is - we want to know the overall age of a machine,
>> for
>> > things like patching schedules etc. (We want to auto-kill machines
>> beyond a
>> > certain age).
>>
>> I thought about this too recently, initially I hoped that we could just
>> return the
>> "create time" of the config file as an really cheap and normally true
>> creation time,
>> but then remembered that our the pmxcfs saves only modification time and
>> sets that
>> for all, atime, mtime, ctime.
>>
>> As a workaround for now, you could use the "description" to save some
>> structured
>> data which includes this info, e.g., in JSON or the like format.
>>
>> I'd be open to have metadata field, maybe it could also host Dominik's
>> tag he has
>> in the works - so we'd only have one such field in the config.
>>
>> cheers,
>> Thomas
>>
>>