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>,
	Stefan Hanreich <s.hanreich@proxmox.com>,
	Daniel Tschlatscher <d.tschlatscher@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager v2 1/2] fix #3719: gui: expose LXC MTU option in web UI
Date: Wed, 16 Nov 2022 20:11:22 +0100	[thread overview]
Message-ID: <dd47e35c-d607-782f-f32a-ca12f1e647b8@proxmox.com> (raw)
In-Reply-To: <5fd1a4f0-8afc-ad12-db52-6a19d42ffced@proxmox.com>

Am 11/11/2022 um 12:14 schrieb Stefan Hanreich:
> Some Notes:
> - Setting the MTU while the container is running, does not update the MTU of
>   the running container. If this is intended behavior it might be smart to
>   document it somewhere or throw a warning. This also doesn't
>   work for the VM patch. Not sure if this is even possible at runtime tbh.
> - Adding a network device when the Container is running with a specific,
>   valid MTU (e.g. 1234) does add the network device to the container, BUT it
>   has a MTU of 1500. Upon reboot the correct MTU is set. Reloading the
>   Network config does not change anything. Maybe just an LXC limitation?
> 

good notes which we should also improve (either implementing it or ensuring
that the change stays pending if it cannot be hot-plugged), but both
pre-existing behavior and so not a blocker for this.

> Code LGTM - small nit: there is still a gettext('MTU') left in the
> NetworkView, but it has been changed in the NetworkInputPanel.
> 
> Reviewed-by: Stefan Hanreich <s.hanreich@proxmox.com>
> Tested-by: Stefan Hanreich <s.hanreich@proxmox.com>

with above applied, thanks!




  reply	other threads:[~2022-11-16 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 15:38 [pve-devel] " Daniel Tschlatscher
2022-11-03 15:38 ` [pve-devel] [PATCH manager v2 2/2] gui: move rate limit field to advanced section Daniel Tschlatscher
2022-11-03 15:38 ` [pve-devel] [PATCH container v2] better parsing for lxc networking mtu setting Daniel Tschlatscher
2022-11-11 11:14 ` [pve-devel] [PATCH manager v2 1/2] fix #3719: gui: expose LXC MTU option in web UI Stefan Hanreich
2022-11-16 19:11   ` Thomas Lamprecht [this message]
2022-11-17 12:52     ` [pve-devel] applied: " Wolfgang Bumiller
2022-11-17 13:13       ` DERUMIER, Alexandre

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=dd47e35c-d607-782f-f32a-ca12f1e647b8@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.tschlatscher@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.hanreich@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