From: Pavel Tide via pve-devel <pve-devel@lists.proxmox.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Pavel Tide <Pavel.TIde@veeam.com>
Subject: Re: [pve-devel] Bug 2582 roadmap
Date: Thu, 12 Sep 2024 09:59:58 +0000 [thread overview]
Message-ID: <mailman.192.1726135803.414.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <IA0PR14MB6767A0575DBA79C4F53006E7939A2@IA0PR14MB6767.namprd14.prod.outlook.com>
[-- Attachment #1: Type: message/rfc822, Size: 12656 bytes --]
From: Pavel Tide <Pavel.TIde@veeam.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: RE: Bug 2582 roadmap
Date: Thu, 12 Sep 2024 09:59:58 +0000
Message-ID: <IA0PR14MB676762136E2CA57D1BFFBE2E93642@IA0PR14MB6767.namprd14.prod.outlook.com>
Hi Proxmox team,
Any updates on the subject? When those changes can be expected in the production version of PVE?
Thanks!
From: Pavel Tide
Sent: Tuesday, September 10, 2024 12:18
To: pve-devel@lists.proxmox.com
Subject: Bug 2582 roadmap
Hi Proxmox team,
Would you provide any delivery estimates on this item?
https://bugzilla.proxmox.com/show_bug.cgi?id=2582
As far as I understand it's been implemented already, but currently stays in the development branch - our lab is up to date and yet we don't see how we can create a separate non-root account to work with PVE cluster.
Please advise,
Thank you!
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next parent reply other threads:[~2024-09-12 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <IA0PR14MB6767A0575DBA79C4F53006E7939A2@IA0PR14MB6767.namprd14.prod.outlook.com>
2024-09-12 9:59 ` Pavel Tide via pve-devel [this message]
2024-09-10 10:18 Pavel Tide via pve-devel
2024-09-13 7:59 ` Fiona Ebner
-- strict thread matches above, loose matches on Subject: below --
2024-09-06 11:17 Pavel Tide via pve-devel
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=mailman.192.1726135803.414.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=Pavel.TIde@veeam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox