public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] www: sdn: improve naming of vm network device in bridge view
Date: Mon, 17 Nov 2025 15:42:59 +0100	[thread overview]
Message-ID: <a8785bb7-fce0-41da-bcbf-95955eb67345@proxmox.com> (raw)
In-Reply-To: <xqij23rplticyzjj6ju4eshakcscsivyfvxxvre3jy56u2gm6n@gjnu4k34cv6n>

Am 17.11.25 um 15:29 schrieb Gabriel Goller:
>>> -            text: gettext('Network Device Index'),
>>> +            text: gettext('VM Network Device'),
>> Is this really limited to VMs or can CTs also be shown? For the latter we
>> might want to use "Guest Network Device"
> CTs can also be shown. Agree, I'll send a new patch!

Thx!

> We also show "VMID" in the other column is that fine for for CTs?

It's a good question, for that we actually use CTID if we're in a context
were we definitively know that it's a CT. For the common case where we
talk about both we most often keep using VMID for that term, mostly
because nobody had a better idea, and it _is_ a shared ID space, so using
different terms for that might also have its disadvantages.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      reply	other threads:[~2025-11-17 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 14:03 Gabriel Goller
2025-11-17 14:25 ` Thomas Lamprecht
2025-11-17 14:30   ` Gabriel Goller
2025-11-17 14:42     ` Thomas Lamprecht [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=a8785bb7-fce0-41da-bcbf-95955eb67345@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal