From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Roland <devzero@web.de>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hrdlicka <s.hrdlicka@proxmox.com>
Subject: Re: [pve-devel] [PATCH firewall/cluster 1/2] fix #1965: cache firewall/cluster.fw file
Date: Thu, 17 Nov 2022 11:38:15 +0100 [thread overview]
Message-ID: <20221117103815.ujlsh3brqoapiuy2@casey.proxmox.com> (raw)
In-Reply-To: <12ddfc25-7445-064e-7c6a-beaacab9d17a@web.de>
On Thu, Nov 17, 2022 at 11:23:19AM +0100, Roland wrote:
> nice!
>
> btw, what about this one ?
>
> https://bugzilla.proxmox.com/show_bug.cgi?id=3909#c3
>
> actually, the firewall stuff is getting blindly executed every 10
> seconds, that's causing a lot of noise.
>
> couldn't/shouldn't this be handled more intelligenty ?
I've been experimenting with a more event-driven approach but I can't
give you an ETA on when that'll happen as it's a lot more involved as it
requires support by our cluster-filesystem (since editing files on
another node needs to properly propagate events all the way through to
the firewall daemon on the other affected nodes), which requires a lot
more scrutiny.
next prev parent reply other threads:[~2022-11-17 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 14:33 [pve-devel] [PATCH firewall/cluster 0/2] cache firewall/cluster.fw Stefan Hrdlicka
2022-10-24 14:33 ` [pve-devel] [PATCH firewall/cluster 1/2] fix #1965: cache firewall/cluster.fw file Stefan Hrdlicka
2022-11-17 9:48 ` Wolfgang Bumiller
[not found] ` <12ddfc25-7445-064e-7c6a-beaacab9d17a@web.de>
2022-11-17 10:38 ` Wolfgang Bumiller [this message]
2022-10-24 14:33 ` [pve-devel] [PATCH firewall/cluster 2/2] register new file firewall/cluster.fw Stefan Hrdlicka
2022-11-17 11:52 ` [pve-devel] applied: " Thomas Lamprecht
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=20221117103815.ujlsh3brqoapiuy2@casey.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=devzero@web.de \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hrdlicka@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.