public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Lou Lecrivain via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Lou Lecrivain <lou.lecrivain@wdz.de>
Subject: [pve-devel] SPAM: [PATCH pve-network 00/16] add support for Nautobot IPAM
Date: Wed, 27 Nov 2024 17:17:47 +0100	[thread overview]
Message-ID: <mailman.781.1732724843.391.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 5040 bytes --]

From: Lou Lecrivain <lou.lecrivain@wdz.de>
To: pve-devel@lists.proxmox.com
Subject: SPAM: [PATCH pve-network 00/16] add support for Nautobot IPAM
Date: Wed, 27 Nov 2024 17:17:47 +0100
Message-ID: <20241127161803.8866-1-lou.lecrivain@wdz.de>

This patch series introduce support for Nautobot as an IPAM.

Please note that:
- Some stuff could still be refined, in my opinion.
  I would be happy to receive some comments, as I'm a
  Perl beginner.
- Test code has not been written *yet*.
- Nautobot itself has some restrictions, for instance
  it does not support IP ranges. So I had to hack
  around this a bit. I'd be happy to only do prefix
  allocations, if that's possible.

MfG
--
Lou Lecrivain, WDZ GmbH

Lou Lecrivain (16):
  ipam: nautobot support initial commit
  ipam: add Nautobot plugin sources to Makefile
  ipam: change verify URL (now common to Nautobot and Netbox)
  ipam: nautobot: add verification for ipam namespace plugin parameter
  ipam: nautobot: fix on_update_hook for NautobotPlugin
  ipam: nautobot: add default active status check
  ipam: nautobot: fix typo
  ipam: nautobot: 1st working "add subnet" and "add ip"
  ipam: nautobot: simplify query
  ipam: nautobot: api endpoint change no longer needed
  ipam: nautobot: add update_ip sub
  ipam: nautobot: add get ips for mac function
  ipam: nautobot: 1st draft for allocating ip in dhcp range
  ipam: nautobot: hacky ip range support
  ipam: nautobot: implement plain prefix allocation (without ranges)
  ipam: nautobot: add word of warning for dhcp range support

 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 | 263 ++++++++++++++++++++
 4 files changed, 268 insertions(+), 1 deletion(-)
 create mode 100644 src/PVE/Network/SDN/Ipams/NautobotPlugin.pm

-- 
2.39.5



[-- 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:[~2024-11-27 16:27 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.781.1732724843.391.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=lou.lecrivain@wdz.de \
    /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