public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Oguz Bektas <o.bektas@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] lxc: add 'unmanaged' checkbox in wizard
Date: Sat, 6 Nov 2021 16:39:41 +0100	[thread overview]
Message-ID: <f6c8301c-17ee-bae6-c8ff-e4849959eb26@proxmox.com> (raw)
In-Reply-To: <YYPnuKuG9032G3nZ@gaia>

On 04.11.21 15:01, Oguz Bektas wrote:
> On Thu, Nov 04, 2021 at 02:58:25PM +0100, Thomas Lamprecht wrote:
>> On 04.11.21 14:19, Oguz Bektas wrote:
>>> to allow creating containers with 'unmanaged' ostype easily in GUI.
>>> that way we can use other unsupported templates in the GUI as well.
>>
>> it's rather an advanced option, but I'm not even sure I want it there,
>> unmanaged CTs are def. not the norm. Is there any user demand for this?
> 
> no feature request or the like.
> but it adds more flexibility to the GUI, e.g. you wouldn't have to
> create your container from the command line when using a custom
> (unsupported) distribution template.

1. it crowds the interface more for an very rare use case that nobody expressed
   their desire  for yet, that alone can often be an anti-feature.

2. more important, it may easily get ticked by unknowing users, as its probably
   not exactly clear what it actually does to a big chunk of users (its not a
   standard action) - especially as one then can still configure the network,
   dns and other things but they simply won't have any effect anymore, that's
   not good UX..

Further, note that we already automatically fall-back to `unmanaged` and also
accept it as unmanaged if denoted as such in the `/etc/os-release` file, that's
enough flexibility for an odd use-case, any user can prepare their archives to
match that, else they can always use the CLI or API.

> 
> i thought about hiding it behind "Advanced" as well but it seems that
> doesn't work at all on the container wizard?

1. If we'd really add it (and I'm not agreeing on that currently), it'd belong
   into the `Template` panel, there the appliance selection (for which this is
   relevant) happens.

2. The advanced mode works in general just fine in the CT wizard, e.g., see the
   Disks and CPU tabs. The advanced mechanism is a shared feature between the
   EditWindow (control the checkbox) and InputPanel (holds the advanced items)
   components, maybe you did not added it in an InputPanel or used the wrong
   config properties, hard to tell without seeing code ;-)




      reply	other threads:[~2021-11-06 15:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 13:19 Oguz Bektas
2021-11-04 13:58 ` Thomas Lamprecht
2021-11-04 14:01   ` Oguz Bektas
2021-11-06 15:39     ` 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=f6c8301c-17ee-bae6-c8ff-e4849959eb26@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=o.bektas@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