public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
	"t.lamprecht@proxmox.com" <t.lamprecht@proxmox.com>,
	"s.hanreich@proxmox.com" <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [RFC cluster/manager/network 0/6] Add support for DHCP servers to SDN
Date: Wed, 13 Sep 2023 13:21:46 +0000	[thread overview]
Message-ID: <30aa87542f4b615aa9f1295b170f26eb8c146ba6.camel@groupe-cyllene.com> (raw)
In-Reply-To: <e2293496-8e93-d42a-bf7a-316ac6b8ee8e@proxmox.com>

> > But it's avoid to call ipam at vm_start. (and could be used for
> > firewall to auto generate ip filtering)
> > 
> 
> Maybe setting it there could just be an interface for setting it in
> the 
> IPAM manually?
> 
yes, use should be able to define his own ip too. (maybe directly in a
ipam gui on the sdn subnet ,   or maybe on the vm nic gui (but
registering ip in ipam),  I'm really not sure ...)


> But yes, the snapshots / backup cases certainly requires some
> thought.
> 
> Another thing I was thinking about: When we create a mapping on start
> / 
> stop we will also have to consider DHCP lease time and cannot 
> immediately re-use the IP (which is actually quite likely if IPAM
> always 
> just returns the next IP in the list). We will have to take into
> account 
> the DHCP lease time in our pve IPAM implementation and reserve the IP
> accordingly.
> 
> For dnsmasq, the dhcp hookscripts might come in handy in that case so
> we 
> know the exact expiration time.
> 
> As Thomas already mentioned, time drift in VMs (e.g. after
> hibernation) 
> can also cause real issues here..
> 
> We would also need some kind of mechanism for cleaning expired
> entries 
> automatically, otherwise local pve IPAM becomes cluttered.
> 

Can't we have simply an infinite lease time,
and simply remove leases manually from dhcp + delete ip from ipam at vm
stop/delete ?




> As far as I can tell, Kea + NetBox integration already supports DHCP 
> reservations, so we should be fine on that front.
> 


  reply	other threads:[~2023-09-13 13:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 13:42 Stefan Hanreich
2023-09-08 13:42 ` [pve-devel] [RFC pve-cluster 1/6] cluster files: add dhcp.cfg Stefan Hanreich
2023-09-08 13:43 ` [pve-devel] [RFC pve-manager 2/6] sdn: regenerate DHCP config on reload Stefan Hanreich
2023-09-08 13:43 ` [pve-devel] [RFC pve-network 3/6] sdn: dhcp: add abstract class for DHCP plugins Stefan Hanreich
2023-09-08 13:43 ` [pve-devel] [RFC pve-network 4/6] sdn: dhcp: subnet: add DHCP options to subnet configuration Stefan Hanreich
2023-09-11  4:03   ` DERUMIER, Alexandre
2023-09-13  8:37     ` Stefan Hanreich
2023-09-08 13:43 ` [pve-devel] [RFC pve-network 5/6] sdn: dhcp: add DHCP plugin for dnsmasq Stefan Hanreich
2023-09-08 13:43 ` [pve-devel] [RFC pve-network 6/6] sdn: dhcp: regenerate config for DHCP servers on reload Stefan Hanreich
2023-09-11  3:53 ` [pve-devel] [RFC cluster/manager/network 0/6] Add support for DHCP servers to SDN DERUMIER, Alexandre
2023-09-13  8:18   ` DERUMIER, Alexandre
2023-09-13  8:54   ` Stefan Hanreich
2023-09-13  9:26     ` DERUMIER, Alexandre
2023-09-13 11:37     ` Thomas Lamprecht
2023-09-13 11:43       ` DERUMIER, Alexandre
2023-09-13 11:50       ` Stefan Hanreich
2023-09-13 12:40         ` Thomas Lamprecht
2023-09-13 12:50         ` DERUMIER, Alexandre
2023-09-13 13:05           ` Stefan Hanreich
2023-09-13 13:21             ` DERUMIER, Alexandre [this message]
2023-09-13 13:48               ` Stefan Hanreich
2023-09-13 13:52                 ` Stefan Hanreich
2023-09-14 13:15                   ` DERUMIER, Alexandre
2023-09-20 21:48               ` DERUMIER, Alexandre
2023-09-26 11:20                 ` Stefan Hanreich
2023-09-26 13:07                   ` DERUMIER, Alexandre
2023-09-26 14:12                     ` Stefan Hanreich
2023-09-26 16:55                       ` DERUMIER, Alexandre

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=30aa87542f4b615aa9f1295b170f26eb8c146ba6.camel@groupe-cyllene.com \
    --to=alexandre.derumier@groupe-cyllene.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.hanreich@proxmox.com \
    --cc=t.lamprecht@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 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