From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH pve-firewall 20/21] api: load sdn ipsets
Date: Wed, 26 Jun 2024 14:34:32 +0200 [thread overview]
Message-ID: <53d9e3c7-a792-4111-ac9c-58b7e7838df2@proxmox.com> (raw)
In-Reply-To: <20240626121550.292290-21-s.hanreich@proxmox.com>
Seems like I regenerated the patches once, after writing a comment so
I'll leave it here:
This is certainly the minimally invasive way to go about this, but it
has the downside of having to load the cluster configuration twice. Once
for validating all rules properly and once for providing the methods
with a cluster config dictionary that doesn't contain the SDN ipsets, so
it can be saved. This didn't pose too much of an issue in my tests, the
API calls were still quite fast.
Passing the configurations from load_conf certainly is a bit hacky,
since we're passing almost the same config twice - but works quite well
for this use case. We only have to do this for the cluster
configuration, since this is the only place where the cluster
configuration gets saved.
On 6/26/24 14:15, Stefan Hanreich wrote:
> Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
> ---
> src/PVE/API2/Firewall/Cluster.pm | 3 ++-
> src/PVE/API2/Firewall/Rules.pm | 18 +++++++++++-------
> src/PVE/API2/Firewall/VM.pm | 3 ++-
> 3 files changed, 15 insertions(+), 9 deletions(-)
>
> diff --git a/src/PVE/API2/Firewall/Cluster.pm b/src/PVE/API2/Firewall/Cluster.pm
> index 48ad90d..3f48431 100644
> --- a/src/PVE/API2/Firewall/Cluster.pm
> +++ b/src/PVE/API2/Firewall/Cluster.pm
> @@ -214,6 +214,7 @@ __PACKAGE__->register_method({
> permissions => {
> check => ['perm', '/', [ 'Sys.Audit' ]],
> },
> + protected => 1,
> parameters => {
> additionalProperties => 0,
> properties => {
> @@ -253,7 +254,7 @@ __PACKAGE__->register_method({
> code => sub {
> my ($param) = @_;
>
> - my $conf = PVE::Firewall::load_clusterfw_conf();
> + my $conf = PVE::Firewall::load_clusterfw_conf(undef, 1);
>
> return PVE::Firewall::Helpers::collect_refs($conf, $param->{type}, "dc");
> }});
> diff --git a/src/PVE/API2/Firewall/Rules.pm b/src/PVE/API2/Firewall/Rules.pm
> index 9fcfb20..ebb51af 100644
> --- a/src/PVE/API2/Firewall/Rules.pm
> +++ b/src/PVE/API2/Firewall/Rules.pm
> @@ -72,6 +72,7 @@ sub register_get_rules {
> path => '',
> method => 'GET',
> description => "List rules.",
> + protected => 1,
> permissions => PVE::Firewall::rules_audit_permissions($rule_env),
> parameters => {
> additionalProperties => 0,
> @@ -120,6 +121,7 @@ sub register_get_rule {
> path => '{pos}',
> method => 'GET',
> description => "Get single rule data.",
> + protected => 1,
> permissions => PVE::Firewall::rules_audit_permissions($rule_env),
> parameters => {
> additionalProperties => 0,
> @@ -412,11 +414,12 @@ sub lock_config {
> sub load_config {
> my ($class, $param) = @_;
>
> + my $sdn_conf = PVE::Firewall::load_clusterfw_conf(undef, 1);
> my $fw_conf = PVE::Firewall::load_clusterfw_conf();
> - my $rules = $fw_conf->{groups}->{$param->{group}};
> + my $rules = $sdn_conf->{groups}->{$param->{group}};
> die "no such security group '$param->{group}'\n" if !defined($rules);
>
> - return (undef, $fw_conf, $rules);
> + return ($sdn_conf, $fw_conf, $rules);
> }
>
> sub save_rules {
> @@ -488,10 +491,11 @@ sub lock_config {
> sub load_config {
> my ($class, $param) = @_;
>
> + my $sdn_conf = PVE::Firewall::load_clusterfw_conf(undef, 1);
> my $fw_conf = PVE::Firewall::load_clusterfw_conf();
> - my $rules = $fw_conf->{rules};
> + my $rules = $sdn_conf->{rules};
>
> - return (undef, $fw_conf, $rules);
> + return ($sdn_conf, $fw_conf, $rules);
> }
>
> sub save_rules {
> @@ -528,7 +532,7 @@ sub lock_config {
> sub load_config {
> my ($class, $param) = @_;
>
> - my $cluster_conf = PVE::Firewall::load_clusterfw_conf();
> + my $cluster_conf = PVE::Firewall::load_clusterfw_conf(undef, 1);
> my $fw_conf = PVE::Firewall::load_hostfw_conf($cluster_conf);
> my $rules = $fw_conf->{rules};
>
> @@ -572,7 +576,7 @@ sub lock_config {
> sub load_config {
> my ($class, $param) = @_;
>
> - my $cluster_conf = PVE::Firewall::load_clusterfw_conf();
> + my $cluster_conf = PVE::Firewall::load_clusterfw_conf(undef, 1);
> my $fw_conf = PVE::Firewall::load_vmfw_conf($cluster_conf, 'vm', $param->{vmid});
> my $rules = $fw_conf->{rules};
>
> @@ -616,7 +620,7 @@ sub lock_config {
> sub load_config {
> my ($class, $param) = @_;
>
> - my $cluster_conf = PVE::Firewall::load_clusterfw_conf();
> + my $cluster_conf = PVE::Firewall::load_clusterfw_conf(undef, 1);
> my $fw_conf = PVE::Firewall::load_vmfw_conf($cluster_conf, 'ct', $param->{vmid});
> my $rules = $fw_conf->{rules};
>
> diff --git a/src/PVE/API2/Firewall/VM.pm b/src/PVE/API2/Firewall/VM.pm
> index 4222103..9800d8c 100644
> --- a/src/PVE/API2/Firewall/VM.pm
> +++ b/src/PVE/API2/Firewall/VM.pm
> @@ -234,6 +234,7 @@ sub register_handlers {
> path => 'refs',
> method => 'GET',
> description => "Lists possible IPSet/Alias reference which are allowed in source/dest properties.",
> + protected => 1,
> permissions => {
> check => ['perm', '/vms/{vmid}', [ 'VM.Audit' ]],
> },
> @@ -278,7 +279,7 @@ sub register_handlers {
> code => sub {
> my ($param) = @_;
>
> - my $cluster_conf = PVE::Firewall::load_clusterfw_conf();
> + my $cluster_conf = PVE::Firewall::load_clusterfw_conf(undef, 1);
> my $fw_conf = PVE::Firewall::load_vmfw_conf($cluster_conf, $rule_env, $param->{vmid});
>
> my $dc_refs = PVE::Firewall::Helpers::collect_refs($cluster_conf, $param->{type}, 'dc');
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-06-26 12:34 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 12:15 [pve-devel] [RFC firewall/proxmox{-ve-rs, -firewall, -perl-rs} 00/21] autogenerate ipsets for sdn objects Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 01/21] debian: add files for packaging Stefan Hanreich
2024-06-27 10:41 ` Gabriel Goller
2024-07-16 16:03 ` Thomas Lamprecht
2024-08-13 16:06 ` Max Carrara
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 02/21] firewall: add ip range types Stefan Hanreich
2024-08-13 16:08 ` Max Carrara
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 03/21] firewall: address: use new iprange type for ip entries Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 04/21] ipset: add range variant to addresses Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 05/21] iprange: add methods for converting an ip range to cidrs Stefan Hanreich
2024-08-13 16:09 ` Max Carrara
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 06/21] ipset: address: add helper methods Stefan Hanreich
2024-06-27 10:45 ` Gabriel Goller
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 07/21] firewall: guest: derive traits according to rust api guidelines Stefan Hanreich
2024-06-27 10:50 ` Gabriel Goller
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 08/21] common: add allowlist Stefan Hanreich
2024-06-27 10:47 ` Gabriel Goller
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 09/21] sdn: add name types Stefan Hanreich
2024-06-27 10:56 ` Gabriel Goller
2024-07-16 9:27 ` Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 10/21] sdn: add ipam module Stefan Hanreich
2024-08-13 16:12 ` Max Carrara
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 11/21] sdn: ipam: add method for generating ipsets Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 12/21] sdn: add config module Stefan Hanreich
2024-06-27 10:54 ` Gabriel Goller
2024-07-16 9:28 ` Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 13/21] sdn: config: add method for generating ipsets Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 14/21] tests: add sdn config tests Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-ve-rs 15/21] tests: add ipam tests Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-firewall 16/21] cargo: update dependencies Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-firewall 17/21] config: tests: add support for loading sdn and ipam config Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-firewall 18/21] ipsets: autogenerate ipsets for vnets and ipam Stefan Hanreich
2024-06-26 12:15 ` [pve-devel] [PATCH pve-firewall 19/21] add support for loading sdn firewall configuration Stefan Hanreich
2024-08-13 16:14 ` Max Carrara
2024-06-26 12:15 ` [pve-devel] [PATCH pve-firewall 20/21] api: load sdn ipsets Stefan Hanreich
2024-06-26 12:34 ` Stefan Hanreich [this message]
2024-06-26 12:15 ` [pve-devel] [PATCH proxmox-perl-rs 21/21] add PVE::RS::Firewall::SDN module Stefan Hanreich
2024-08-13 16:14 ` Max Carrara
2024-06-28 13:46 ` [pve-devel] [RFC firewall/proxmox{-ve-rs, -firewall, -perl-rs} 00/21] autogenerate ipsets for sdn objects Gabriel Goller
2024-07-16 9:33 ` Stefan Hanreich
2024-08-13 16:06 ` Max Carrara
2024-09-24 8:41 ` Thomas Lamprecht
2024-10-10 15:59 ` Stefan Hanreich
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=53d9e3c7-a792-4111-ac9c-58b7e7838df2@proxmox.com \
--to=s.hanreich@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 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.