From: Leo Nunner <l.nunner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH RFC container manager] Introduce cloud-init support for LXC
Date: Thu, 11 May 2023 13:12:44 +0200 [thread overview]
Message-ID: <20230511111249.171748-1-l.nunner@proxmox.com> (raw)
This series introduces basic cloudinit support for containers. All in
all, it works quite similar to VMs, with the caveat that we only allow
network configuration through the alrady existing systems, and not via
cloud-init.
These patches should still be seen as WIP, but they are in a workable
state and I'd like some feedback on how I currently handle things. Are
there any other parameters/features that are needed here? Is the current
mechanism for providing the configuration to the container optimal, or
is there a better way?
container:
Leo Nunner (3):
cloudinit: introduce config parameters
cloudinit: basic implementation
cloudinit: add dump command to pct
src/PVE/API2/LXC.pm | 36 +++++++++++
src/PVE/API2/LXC/Config.pm | 7 ++-
src/PVE/CLI/pct.pm | 4 ++
src/PVE/LXC.pm | 1 +
src/PVE/LXC/Cloudinit.pm | 125 +++++++++++++++++++++++++++++++++++++
src/PVE/LXC/Config.pm | 61 ++++++++++++++++++
src/PVE/LXC/Makefile | 1 +
src/lxc-pve-prestart-hook | 5 ++
8 files changed, 239 insertions(+), 1 deletion(-)
create mode 100644 src/PVE/LXC/Cloudinit.pm
manager:
Leo Nunner (2):
cloudinit: rename qemu cloudinit panel
cloudinit: introduce panel for LXCs
www/manager6/Makefile | 1 +
www/manager6/lxc/CloudInit.js | 219 +++++++++++++++++++++++++++++++++
www/manager6/lxc/Config.js | 6 +
www/manager6/qemu/CloudInit.js | 4 +-
www/manager6/qemu/Config.js | 2 +-
5 files changed, 229 insertions(+), 3 deletions(-)
create mode 100644 www/manager6/lxc/CloudInit.js
--
2.30.2
next reply other threads:[~2023-05-11 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 11:12 Leo Nunner [this message]
2023-05-11 11:12 ` [pve-devel] [PATCH RFC container 1/3] cloudinit: introduce config parameters Leo Nunner
2023-05-11 11:12 ` [pve-devel] [PATCH RFC container 2/3] cloudinit: basic implementation Leo Nunner
2023-05-11 11:12 ` [pve-devel] [PATCH RFC container 3/3] cloudinit: add dump command to pct Leo Nunner
2023-05-11 11:12 ` [pve-devel] [PATCH RFC manager 1/2] cloudinit: rename qemu cloudinit panel Leo Nunner
2023-05-11 11:12 ` [pve-devel] [PATCH RFC manager 2/2] cloudinit: introduce panel for LXCs Leo Nunner
2023-05-12 11:39 ` [pve-devel] [PATCH RFC container manager] Introduce cloud-init support for LXC Wolfgang Bumiller
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=20230511111249.171748-1-l.nunner@proxmox.com \
--to=l.nunner@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