From: Lou Lecrivain via pve-devel <pve-devel@lists.proxmox.com>
To: <pve-devel@lists.proxmox.com>
Cc: Lou.Lecrivain@wdz.de, me@nurohman.com
Subject: Re: [pve-devel] [PATCH pve-network] Fix #5496: NetBox add ip range
Date: Fri, 13 Dec 2024 09:55:18 +0000 [thread overview]
Message-ID: <mailman.174.1734083759.332.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <mailman.156.1733988042.332.pve-devel@lists.proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 12849 bytes --]
From: <Lou.Lecrivain@wdz.de>
To: <pve-devel@lists.proxmox.com>
Cc: <alexandre.derumier@groupe-cyllene.com>, <me@nurohman.com>
Subject: RE: Re: [pve-devel] [PATCH pve-network] Fix #5496: NetBox add ip range
Date: Fri, 13 Dec 2024 09:55:18 +0000
Message-ID: <BE1P281MB21167501F2324FB4980D1E82853F2@BE1P281MB2116.DEUP281.PROD.OUTLOOK.COM>
Re,
> but shouldn't theses ranges be added when the dhcp ranges are submitted
> on subnet create/update api call ? (I'm not 100% sure, but I think it
> was missing a hook to call the sdn api when submitting the dhcp ranges)
Yes, I do think this should be the case too.
BR
________________________________________
De : pve-devel <pve-devel-bounces@lists.proxmox.com> de la part de DERUMIER, Alexandre via pve-devel <pve-devel@lists.proxmox.com>
Envoyé : jeudi 12 décembre 2024 08:20
À : pve-devel@lists.proxmox.com <pve-devel@lists.proxmox.com>
Cc : DERUMIER, Alexandre <alexandre.derumier@groupe-cyllene.com>; me@nurohman.com <me@nurohman.com>
Objet : [!!ACHTUNG extern!!] - Re: [pve-devel] [PATCH pve-network] Fix #5496: NetBox add ip range
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[-- 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
next prev parent reply other threads:[~2024-12-13 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 23:38 nurohman via pve-devel
2024-12-12 7:20 ` DERUMIER, Alexandre via pve-devel
2024-12-13 9:55 ` Lou Lecrivain via pve-devel [this message]
[not found] ` <b6d41bd46ba97b50da21589f2ea676ab34cac339.camel@groupe-cyllene.com>
2024-12-12 13:17 ` Stefan Hanreich
[not found] <20241211233832.806187-1-me@nurohman.com>
2024-12-12 13:20 ` 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=mailman.174.1734083759.332.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=Lou.Lecrivain@wdz.de \
--cc=me@nurohman.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