From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 22D2371CEA for ; Fri, 21 May 2021 19:37:03 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0F75711253 for ; Fri, 21 May 2021 19:36:33 +0200 (CEST) Received: from mailhost2.inet.dkfz-heidelberg.de (mailhost2.inet.dkfz-heidelberg.de [193.174.53.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id E932111242 for ; Fri, 21 May 2021 19:36:31 +0200 (CEST) Received: from mx-ext.inet.dkfz-heidelberg.de (mx-ext.inet.dkfz-heidelberg.de [192.54.49.101]) by mailhost2.inet.dkfz-heidelberg.de (8.14.7/8.14.7) with ESMTP id 14LHRv79022465 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 21 May 2021 19:27:57 +0200 X-Virus-Scanned-DKFZ: amavisd-new at dkfz-heidelberg.de Received: from vpngate1144.inet.dkfz-heidelberg.de ([193.174.55.143]) (authenticated bits=0) by mx-ext.inet.dkfz-heidelberg.de (8.14.7/8.14.7/smtpin) with ESMTP id 14LHRtwV028577 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 21 May 2021 19:27:55 +0200 DKIM-Filter: OpenDKIM Filter v2.11.0 mx-ext.inet.dkfz-heidelberg.de 14LHRtwV028577 To: Proxmox VE user list From: Frank Thommen Organization: DKFZ Heidelberg, Omics IT and Data Management Core Facility (ODCF) Message-ID: <50af38a6-2fe5-0e24-4d12-672d79e4b667@dkfz-heidelberg.de> Date: Fri, 21 May 2021 19:27:54 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mx-ext.inet.dkfz-heidelberg.de [192.54.49.101]); Fri, 21 May 2021 19:27:55 +0200 (CEST) X-Spam-Status: No, score=-100.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx-ext.inet.dkfz-heidelberg.de X-SPAM-LEVEL: Spam detection results: 0 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [PVE-User] "Naming" of containers X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 May 2021 17:37:03 -0000 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 -vm###, 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