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 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
