From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 qemu-server 0/9] RFC: sdn: add ipam support
Date: Mon, 12 Jul 2021 00:46:58 +0200 [thread overview]
Message-ID: <20210711224707.63089-1-aderumier@odiso.com> (raw)
Hi,
This is an RFC to implement ipam support on qemu-server.
This don't change the cloud-init current working.
As I need to manage pending ip registration configuration, to follow the pending netX interfaces.
I have added ip,ip6,gw,gw6 field to netX interfaces options. (same than LXC).
(as current ipconfigX pending, is pending cloudinit generation)
so the workflow is:
--> update netX=...,ip=....
--> ip is registered as pending
--> hotplug/coldplug succesful
---> pending ip replace current conf oldip
---->the ip set in cloudinit pending ipconfigX
------> cloudinit regeneration
---> ipconfigX is remove from pending
As documentation said than ipconfigX is for cloudinit config,
I think it could be ok.
Some users could use the sdn features without cloudinit(allow some subnets only, and autogenerate firewall ipfilter).
Also, for ipam, I need bridge && mac from the netX, and ip need to follow pending states of the nic.
Changelog v2:
- rebase on last master / proxmox7
- fix handling errors when multiple nics are hotplugged at same time
- keep ip address in ipam if snapshots reference it
- only update dns when pending ip is apply (need new pve-network patch)
- implement snapshot rollback/delete
- implement vm create/destroy
todo : implement backup restore
Alexandre Derumier (9):
add ipam module
add print_ipconfig
add ip options to netdescr
ipam : add update/delete support
ipam : add revert ip support
ipam : add snapshot rollback support
ipam : add snaphot delete support
ipam : add create vm support
ipam : add destroy vm support
PVE/API2/Qemu.pm | 56 +++++++++-
PVE/QemuConfig.pm | 32 ++++++
PVE/QemuServer.pm | 228 ++++++++++++++++++++++++++++++++++++++++
PVE/QemuServer/Ipam.pm | 141 +++++++++++++++++++++++++
PVE/QemuServer/Makefile | 1 +
5 files changed, 457 insertions(+), 1 deletion(-)
create mode 100644 PVE/QemuServer/Ipam.pm
--
2.30.2
next reply other threads:[~2021-07-11 22:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 22:46 Alexandre Derumier [this message]
2021-07-11 22:46 ` [pve-devel] [PATCH v2 qemu-server 1/9] add ipam module Alexandre Derumier
2021-07-11 22:47 ` [pve-devel] [PATCH v2 qemu-server 2/9] add print_ipconfig Alexandre Derumier
2021-07-11 22:47 ` [pve-devel] [PATCH v2 qemu-server 3/9] add ip options to netdescr Alexandre Derumier
2021-07-11 22:47 ` [pve-devel] [PATCH v2 qemu-server 4/9] ipam : add update/delete support Alexandre Derumier
2021-07-11 22:47 ` [pve-devel] [PATCH v2 qemu-server 5/9] ipam : add revert ip support Alexandre Derumier
2021-07-11 22:47 ` [pve-devel] [PATCH v2 qemu-server 6/9] ipam : add snapshot rollback support Alexandre Derumier
2021-07-11 22:47 ` [pve-devel] [PATCH v2 qemu-server 7/9] ipam : add snaphot delete support Alexandre Derumier
2021-07-11 22:47 ` [pve-devel] [PATCH v2 qemu-server 8/9] ipam : add create vm support Alexandre Derumier
2021-07-11 22:47 ` [pve-devel] [PATCH v2 qemu-server 9/9] ipam : add destroy " Alexandre Derumier
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=20210711224707.63089-1-aderumier@odiso.com \
--to=aderumier@odiso.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