From: Frank Thommen <f.thommen@dkfz-heidelberg.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: [PVE-User] "Naming" of containers
Date: Fri, 21 May 2021 19:27:54 +0200 [thread overview]
Message-ID: <50af38a6-2fe5-0e24-4d12-672d79e4b667@dkfz-heidelberg.de> (raw)
Dear all,
is there a way to name a container in PVE, so that this name is findable
through the "Search" form in the PVE dashboard?
By policy all VMs and containers have DNS names like <unit>-vm###,
<unit> being an organizational unit at our institution. The function of
the VM or container is documented in the "Notes" field, which
unfortunately cannot be searched. For VMs it is possible to set a name
which is different from the DNS name. For VMs we have searchable
one-word "names" which describe the VMs function. This is not possible
for containers. Meaning that we have to keep a separate list to map
container (DNS) names to functions. This is tedious and error-prone in
maintenance and cumbersome in usage.
Is there a way to give containers a name different from their DNS name
which is searchable through the PVE dashboard?
We are currently running PVE 6.3-3.
Thanks in advance
Frank
reply other threads:[~2021-05-21 17:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50af38a6-2fe5-0e24-4d12-672d79e4b667@dkfz-heidelberg.de \
--to=f.thommen@dkfz-heidelberg.de \
--cc=pve-user@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