From: Victor Hooi <victorhooi@yahoo.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: PVE development discussion <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] Adding creation time as metadata field to VM/containers?
Date: Wed, 8 Jul 2020 12:04:07 +1000 [thread overview]
Message-ID: <CAMnnoUKfovFLQgzHW2X7L=n0_QF2SCq2oc0kL3e1B_Gmh7p-7Q@mail.gmail.com> (raw)
In-Reply-To: <5908dc13-2ea3-47df-6346-88832a349f44@proxmox.com>
Of course - I understand.
I filed https://bugzilla.proxmox.com/show_bug.cgi?id=2830
Also, if you can think of a cheap hack/workaround that might allow us to
get that data for now, let me know.
On Tue, Jul 7, 2020 at 7:37 PM Thomas Lamprecht <t.lamprecht@proxmox.com>
wrote:
> Hi,
>
> On 06.07.20 22:45, Victor Hooi wrote:
> > 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?
>
> https://lists.proxmox.com/pipermail/pve-devel/2019-October/039349.html
>
> > How difficult would this be to add?
>
> A few places to look at to get all VM/CT creation sides, also, handling
> special cases like backup-restore, cloning, ... needs some thought.
> So nothing really hard, but lots of little details.
>
> You can open a enhancement request over at https://bugzilla.proxmox.com/
> but it probably won't have a high priority from our side.
>
> cheers,
> Thomas
>
>
prev parent reply other threads:[~2020-07-08 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMnnoUJKChvA_j4zinAp3=4S49CikhaFRepb5LSZGBoFvAA1ug.ref@mail.gmail.com>
[not found] ` <CAMnnoUJKChvA_j4zinAp3=4S49CikhaFRepb5LSZGBoFvAA1ug@mail.gmail.com>
[not found] ` <275c1d78-1200-522b-563f-bba257f86ffe@proxmox.com>
[not found] ` <CAMnnoUJhh=y4JwffX0RP=WWoym=BVE_LiusaGF-AewMFbx2Qgg@mail.gmail.com>
[not found] ` <CAMnnoUKA6kU0+ztFQYRs0MMwWiw6exOHpfOmk9W=Hk-oRrnoww@mail.gmail.com>
2020-07-07 9:37 ` Thomas Lamprecht
2020-07-08 2:04 ` Victor Hooi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMnnoUKfovFLQgzHW2X7L=n0_QF2SCq2oc0kL3e1B_Gmh7p-7Q@mail.gmail.com' \
--to=victorhooi@yahoo.com \
--cc=pve-devel@pve.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.