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: Tue, 26 Sep 2023 16:55:28 +0000	[thread overview]
Message-ID: <088c8011bdba7a5cf8fba5573a739ac2936bee69.camel@groupe-cyllene.com> (raw)
In-Reply-To: <a5f92162-2608-52d3-404f-e91a3bae7d78@proxmox.com>

Le mardi 26 septembre 2023 à 16:12 +0200, Stefan Hanreich a écrit :
> > Yes, this is my main concern, as it'll be my case in production, as
> > I
> > managing multiple clusters, on differents location, with subnets
> > sharing.
> > 
> > for me, it's ok if ipam is down when allocating a new ip or vm.
> > But for vm start/stop, I think we should have at minimum some cache
> > somewhere. (I'm think about a disaster recovery or big network
> > problem,
> > where you want to fast restart all vms without need to call the
> > ipam).
> > 
> > Maybe a way, could be to use the local pve ipam, as a local mirror
> > of
> > the external ipam ?    (and don't store ip in vm config, but only
> > in
> > pve ipam, the source of truth)
> > 
> 
> Yes, I think this would be preferrable over the VM config. This also
> means we would have to sync from netbox to local PVE IPAMs?

See my pseudo algorithm, I think we can sync on the fly from netbox to
local pveipam (like a read cache), when we allocate a new ip.

I think it's not a problem with multiple cluster with different local
pveipam, if we always try to allocate a new ip from the external ip,
then write it to local pveipam, for later read.

Maybe it could be improve with a full sync of subnets in cron ? (Need
to check the external ipam apis)





> 
> > I'm a bit busy currently on other stuff and I would like to finish
> > them
> > first. 
> > 
> > So if you have a little bit time to work on this, it could be great
> > :)
> > 
> > I have send some patches in 2021 for ipam integration in qemu/lxc,
> > if
> > you want to take some inspiration. (without the ip in the vm
> > config, it
> > should be a lot easier)
> > 
> 
> I'll try to get on it then, I'll still be here for 2,5 weeks until I
> go
> on a longer vacation. Hopefully I'll get something workable ready
> until
> then. I will look into your patches - thanks for the hint!
> 
I'll have a little bit more time next week , then I'm going to do some
proxmox training with students, so I'll be busy until mid-october.
(so when you'll be in vacation ^_^).

If you have some early patches for this time, I'll be able to continue
the work if needed.



> > Yes,admin should be able to see allocated ip. (like a real ipam).
> > 
> > I was thinking about other stuff for later, but maybe it could be
> > great
> > for an admin to be able to reserve ips and put them in a pool.
> > Then user could choose ip from this pool.
> > 
> > (Usecase is public ip addresses, where a customer could buy some of
> > them,
> > then allocated them like he want)
> > 
> 
> That sounds like a great feature for hosters, I'll certainly look
> into that.
> 


      reply	other threads:[~2023-09-26 16:56 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
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 [this message]

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=088c8011bdba7a5cf8fba5573a739ac2936bee69.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