From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container v3 1/3] add the CT profiles plugin
Date: Thu, 16 Nov 2023 15:09:18 +0100 [thread overview]
Message-ID: <20231116140921.3854429-7-d.csapak@proxmox.com> (raw)
In-Reply-To: <20231116140921.3854429-1-d.csapak@proxmox.com>
simply uses the json_config_properties for the ct config and maps them
to "ct_${opt}"
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
src/PVE/Makefile | 1 +
src/PVE/Profiles/CT.pm | 28 ++++++++++++++++++++++++++++
src/PVE/Profiles/Makefile | 4 ++++
3 files changed, 33 insertions(+)
create mode 100644 src/PVE/Profiles/CT.pm
create mode 100644 src/PVE/Profiles/Makefile
diff --git a/src/PVE/Makefile b/src/PVE/Makefile
index 40742e4..e9ad9a3 100644
--- a/src/PVE/Makefile
+++ b/src/PVE/Makefile
@@ -8,5 +8,6 @@ install: ${SOURCES}
make -C LXC install
make -C VZDump install
make -C CLI install
+ make -C Profiles install
diff --git a/src/PVE/Profiles/CT.pm b/src/PVE/Profiles/CT.pm
new file mode 100644
index 0000000..513fad4
--- /dev/null
+++ b/src/PVE/Profiles/CT.pm
@@ -0,0 +1,28 @@
+package PVE::Profiles::CT;
+
+use strict;
+use warnings;
+
+use PVE::Profiles::Plugin;
+use PVE::LXC::Config;
+
+use base qw(PVE::Profiles::Plugin);
+
+sub type {
+ return "ct";
+}
+
+sub properties {
+ return PVE::LXC::Config::json_config_properties();
+}
+
+sub options {
+ my $props = PVE::LXC::Config::json_config_properties();
+ my $opts = {};
+ for my $opt (keys $props->%*) {
+ $opts->{$opt} = { optional => 1 };
+ }
+ return $opts;
+}
+
+1;
diff --git a/src/PVE/Profiles/Makefile b/src/PVE/Profiles/Makefile
new file mode 100644
index 0000000..e63a9f2
--- /dev/null
+++ b/src/PVE/Profiles/Makefile
@@ -0,0 +1,4 @@
+
+.PHONY: install
+install:
+ install -D -m 0644 CT.pm ${PERLDIR}/PVE/Profiles/CT.pm
--
2.30.2
next prev parent reply other threads:[~2023-11-16 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 14:09 [pve-devel] [PATCH cluster/guest-common/qemu-server/container/manager v2] add backend profile support Dominik Csapak
2023-11-16 14:09 ` [pve-devel] [PATCH cluster v3 1/1] add profiles.cfg to cluster fs Dominik Csapak
2023-11-16 14:09 ` [pve-devel] [PATCH guest-common v3 1/1] add profiles section config plugin Dominik Csapak
2023-11-16 14:09 ` [pve-devel] [PATCH qemu-server v3 1/3] add the VM profiles plugin Dominik Csapak
2023-11-16 14:09 ` [pve-devel] [PATCH qemu-server v3 2/3] api: add profile option to create vm api call Dominik Csapak
2023-11-16 14:09 ` [pve-devel] [PATCH qemu-server v3 3/3] qm: register and init the profiles plugins Dominik Csapak
2023-11-16 14:09 ` Dominik Csapak [this message]
2023-11-16 14:09 ` [pve-devel] [PATCH container v3 2/3] api: add profile option to create ct api call Dominik Csapak
2023-11-16 14:09 ` [pve-devel] [PATCH container v3 3/3] pct: register and init the profiles plugins Dominik Csapak
2023-11-16 14:09 ` [pve-devel] [PATCH manager v3 1/1] api: add guest profile api endpoint Dominik Csapak
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=20231116140921.3854429-7-d.csapak@proxmox.com \
--to=d.csapak@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