From: Lou Lecrivain via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: lou.lecrivain@orange.fr
Subject: [pve-devel] [PATCH pve-network v6 0/2] ipam plugin for nautobot >= 2.4.14
Date: Mon, 22 Sep 2025 11:19:38 +0200 [thread overview]
Message-ID: <mailman.223.1758532792.390.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 5410 bytes --]
From: lou.lecrivain@orange.fr
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-network v6 0/2] ipam plugin for nautobot >= 2.4.14
Date: Mon, 22 Sep 2025 11:19:38 +0200
Message-ID: <20250922091942.4715-1-lou.lecrivain@orange.fr>
From: Lou Lecrivain <lou.lecrivain@wdz.de>
Dear maintainers,
Following last review rounds of Nautobot IPAM plugin, we concluded that
it was not possible to have it fully working as expected due to lack of IP
range support in Nautobot IPAM.
In the meantime, I was able to upstream a PR to Nautobot for
allocating IPs within a range, which was released with nautobot 2.4.14.
https://github.com/nautobot/nautobot/releases/tag/v2.4.14
This (rebased and edited) version of the Nautobot IPAM plugin includes
the necessary logic to use the new allocation scheme. Please note that
I also had to include a version check, as this is incompatible with
previous versions of Nautobot.
BR
Lou Lecrivain (2):
ipam: add Nautobot plugin
ipam: add test cases for nautobot plugin
src/PVE/API2/Network/SDN/Ipams.pm | 1 +
src/PVE/Network/SDN/Ipams.pm | 3 +
src/PVE/Network/SDN/Ipams/Makefile | 2 +-
src/PVE/Network/SDN/Ipams/NautobotPlugin.pm | 460 ++++++++++++++++++
src/test/ipams/nautobot/expected.add_ip | 11 +
.../ipams/nautobot/expected.add_ip_notgateway | 11 +
.../ipams/nautobot/expected.add_next_freeip | 11 +
src/test/ipams/nautobot/expected.add_subnet | 11 +
src/test/ipams/nautobot/expected.del_ip | 11 +
src/test/ipams/nautobot/expected.update_ip | 11 +
src/test/ipams/nautobot/ipam_config | 24 +
src/test/ipams/nautobot/sdn_config | 20 +
src/test/ipams/netbox/ipam_config | 8 +-
src/test/ipams/phpipam/ipam_config | 8 +-
14 files changed, 589 insertions(+), 3 deletions(-)
create mode 100644 src/PVE/Network/SDN/Ipams/NautobotPlugin.pm
create mode 100644 src/test/ipams/nautobot/expected.add_ip
create mode 100644 src/test/ipams/nautobot/expected.add_ip_notgateway
create mode 100644 src/test/ipams/nautobot/expected.add_next_freeip
create mode 100644 src/test/ipams/nautobot/expected.add_subnet
create mode 100644 src/test/ipams/nautobot/expected.del_ip
create mode 100644 src/test/ipams/nautobot/expected.update_ip
create mode 100644 src/test/ipams/nautobot/ipam_config
create mode 100644 src/test/ipams/nautobot/sdn_config
--
2.47.3
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-09-22 9:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.223.1758532792.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=lou.lecrivain@orange.fr \
/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