From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 container] api: network: get interfaces from containers
Date: Tue, 14 Nov 2023 19:23:10 +0100 [thread overview]
Message-ID: <9724b837-687f-4e83-89a3-547f0a918009@proxmox.com> (raw)
In-Reply-To: <20230615094333.66179-2-l.nunner@proxmox.com>
Am 15/06/2023 um 11:43 schrieb Leo Nunner:
> Adds an 'interfaces' endpoint in the API
> (/nodes/{node}/lxc/{vmid}/interfaces'), which returns a list of
> interface names, together with a MAC, IPv4 and IPv6 address. This list
> may be expanded in the future. Note that this is only returned for
> *running* containers, stopped containers simply return an empty list.
>
> Signed-off-by: Leo Nunner <l.nunner@proxmox.com>
> ---
> src/PVE/API2/LXC.pm | 50 +++++++++++++++++++++++++++++++++++++++++++++
> src/PVE/LXC.pm | 26 +++++++++++++++++++++++
> 2 files changed, 76 insertions(+)
>
>
applied this one for now, thanks! UI might need slight rework/follow-up, as
this was done before we had the extra line for "is-unprivileged" in the status
panel, so there's not enough space left now.
next prev parent reply other threads:[~2023-11-14 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 9:43 [pve-devel] [PATCH v2 container manager] Show dynamic container IPs in GUI Leo Nunner
2023-06-15 9:43 ` [pve-devel] [PATCH v2 container] api: network: get interfaces from containers Leo Nunner
2023-11-14 16:43 ` DERUMIER, Alexandre
2023-11-14 17:00 ` Thomas Lamprecht
2023-11-14 17:34 ` DERUMIER, Alexandre
2023-11-14 18:23 ` Thomas Lamprecht [this message]
2023-06-15 9:43 ` [pve-devel] [PATCH v2 manager 1/2] lxc: show dynamically assigned IPs in network tab Leo Nunner
2023-11-15 20:51 ` DERUMIER, Alexandre
2023-06-15 9:43 ` [pve-devel] [PATCH v2 manager 2/2] lxc: show IPs in summary view Leo Nunner
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=9724b837-687f-4e83-89a3-547f0a918009@proxmox.com \
--to=t.lamprecht@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