From: Stefan Lendl <s.lendl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH network/container/qemu-server 0/3] sdn: register a new IP at VM start if missing
Date: Tue, 21 Nov 2023 15:55:53 +0100 [thread overview]
Message-ID: <20231121145556.436743-1-s.lendl@proxmox.com> (raw)
If a VM or LXC starts and no IP was found in the IPAM, register a new one.
This is very seful as a fallback if for some reason an IP mapping was deleted
or there is a bug somewhere that does not register an IP.
This acts more like DHCP to allocate an IP on demand.
Special case that is not covered:
If a subnet with IPv4 exists and VMs are present, adding a new subnet with
IPv6, this will not register an IPv6. And vice-versa.
pve-network:
Stefan Lendl (1):
sdn: register MAC in IPAM if not found
src/PVE/Network/SDN/Vnets.pm | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
pve-container:
Stefan Lendl (1):
sdn: pass vmid and hostname to add_dhcp_mapping
src/PVE/LXC.pm | 4 ++--
src/lxc-pve-prestart-hook | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
qemu-server:
Stefan Lendl (1):
sdn: pass vmid and hostname to add_dhcp_mapping
PVE/QemuServer.pm | 2 +-
vm-network-scripts/pve-bridge | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
Summary over all repositories:
5 files changed, 14 insertions(+), 8 deletions(-)
--
murpp v0.4.0
next reply other threads:[~2023-11-21 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 14:55 Stefan Lendl [this message]
2023-11-21 14:55 ` [pve-devel] [PATCH pve-network 1/3] sdn: register MAC in IPAM if not found Stefan Lendl
2023-11-21 14:55 ` [pve-devel] [PATCH pve-container 2/3] sdn: pass vmid and hostname to add_dhcp_mapping Stefan Lendl
2023-11-21 17:49 ` Stefan Hanreich
2023-11-21 14:55 ` [pve-devel] [PATCH qemu-server 3/3] " Stefan Lendl
2023-11-21 19:57 ` [pve-devel] applied-series: [PATCH network/container/qemu-server 0/3] sdn: register a new IP at VM start if missing Thomas Lamprecht
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=20231121145556.436743-1-s.lendl@proxmox.com \
--to=s.lendl@proxmox.com \
--cc=pve-devel@lists.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