From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Bug 2582 roadmap
Date: Fri, 13 Sep 2024 09:59:11 +0200 [thread overview]
Message-ID: <f2225be9-5710-4d0f-a0d9-9b4809df06d0@proxmox.com> (raw)
In-Reply-To: <mailman.139.1725963502.414.pve-devel@lists.proxmox.com>
Hi Pavel,
Am 10.09.24 um 12:18 schrieb Pavel Tide via pve-devel:
> 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.
>
a patch series had been proposed, but the implementation was not
finished AFAIK, see Fabian's review[0]. Since Oguz left the company,
nobody else has picked up work on the series yet. Maybe you can describe
what exactly your use case is, which privileges you'd need in
particular. Of course, proposing patches for what you need (or a rebased
version of Oguz's full series) is welcome too :)
[0]:
https://lore.proxmox.com/pve-devel/1658908014.zeyifvlr1o.astroid@nora.none/
Best Regards,
Fiona
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-09-13 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 10:18 Pavel Tide via pve-devel
2024-09-13 7:59 ` Fiona Ebner [this message]
[not found] <IA0PR14MB6767A0575DBA79C4F53006E7939A2@IA0PR14MB6767.namprd14.prod.outlook.com>
2024-09-12 9:59 ` Pavel Tide via pve-devel
-- 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=f2225be9-5710-4d0f-a0d9-9b4809df06d0@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox