public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH guest-common v4 1/1] add profiles section config plugin
Date: Fri, 17 Nov 2023 12:45:41 +0100	[thread overview]
Message-ID: <20231117114548.3208470-3-d.csapak@proxmox.com> (raw)
In-Reply-To: <20231117114548.3208470-1-d.csapak@proxmox.com>

this is intended to house custom profiles which can be used
on guest creation instead of manually needing to specify every option.

we do special things here:
* we always set 'allow_unknown' to 1, because when using the guest
  specific parts in the cli, we cannot depend on the other one, else
  we'd get a cyclic dependency, and without that we need to ignore
  unknown sections

* we add the 'profile-description' to the options of all registered
  plugins (so we don't have to do it manually)

* we always call 'init(property_isolation => 1)' of the SectionConfig so we cannot forget that

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
 src/Makefile               |  2 +
 src/PVE/Profiles/Plugin.pm | 83 ++++++++++++++++++++++++++++++++++++++
 2 files changed, 85 insertions(+)
 create mode 100644 src/PVE/Profiles/Plugin.pm

diff --git a/src/Makefile b/src/Makefile
index cbc40c1..d99645c 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -17,6 +17,8 @@ install: PVE
 	install -d ${PERL5DIR}/PVE/Mapping
 	install -m 0644 PVE/Mapping/PCI.pm ${PERL5DIR}/PVE/Mapping/
 	install -m 0644 PVE/Mapping/USB.pm ${PERL5DIR}/PVE/Mapping/
+	install -d ${PERL5DIR}/PVE/Profiles
+	install -m 0644 PVE/Profiles/Plugin.pm ${PERL5DIR}/PVE/Profiles/
 	install -d ${PERL5DIR}/PVE/VZDump
 	install -m 0644 PVE/VZDump/Plugin.pm ${PERL5DIR}/PVE/VZDump/
 	install -m 0644 PVE/VZDump/Common.pm ${PERL5DIR}/PVE/VZDump/
diff --git a/src/PVE/Profiles/Plugin.pm b/src/PVE/Profiles/Plugin.pm
new file mode 100644
index 0000000..717383b
--- /dev/null
+++ b/src/PVE/Profiles/Plugin.pm
@@ -0,0 +1,83 @@
+package PVE::Profiles::Plugin;
+
+use strict;
+use warnings;
+
+use PVE::Cluster qw(cfs_register_file);
+use PVE::SectionConfig;
+
+use base qw(PVE::SectionConfig);
+
+my $CFG_PATH = 'virtual-guest/profiles.cfg';
+
+cfs_register_file(
+    $CFG_PATH,
+    sub { __PACKAGE__->parse_config(@_); },
+    sub { __PACKAGE__->write_config(@_); }
+);
+
+my $defaultData = {
+    propertyList => {
+	type => { description => 'Profile type.' },
+	id => {
+	    type => 'string',
+	    description => "The ID of the profile.",
+	    format => 'pve-configid',
+	},
+	'profile-description' => {
+	    description => "Use this to add a short comment about a profile.",
+	    type => 'string',
+	    optional => 1,
+	    maxLength => 128,
+	},
+    },
+};
+
+sub private {
+    return $defaultData;
+}
+
+sub parse_config {
+    my ($class, $filename, $raw, $allow_unknown) = @_;
+
+    # always allow unknown section types, so that qemu-server/pct-container
+    # can parse the file without loading the other plugin type
+    return $class->SUPER::parse_config($filename, $raw, 1);
+}
+
+sub write_config {
+    my ($class, $filename, $cfg, $allow_unknown) = @_;
+
+    return $class->SUPER::write_config($filename, $cfg, 1);
+}
+
+# gets, checks and prepares the guest config
+# throws an error if it does not exist or the type is wrong
+sub load_profile {
+    my ($profile_id, $profile_type) = @_;
+
+    my $cfg = PVE::Cluster::cfs_read_file($CFG_PATH);
+
+    my $profile = $cfg->{ids}->{$profile_id};
+    die "no such profile '$profile_id'\n" if !defined $profile;
+    die "wrong type '$profile->{type}'\n" if $profile->{type} ne $profile_type;
+
+    delete $profile->{type};
+    delete $profile->{'profile-description'};
+
+    return $profile;
+}
+
+# override so we can add the profile description to all sub classes
+sub init {
+    my ($class) = @_;
+
+    $class->SUPER::init(property_isolation => 1);
+
+    my $pdata = $class->private();
+    for my $type (keys $pdata->{plugins}->%*) {
+	$pdata->{options}->{$type}->{'profile-description'} = { optional => 1 };
+    }
+}
+
+1;
-- 
2.30.2





  parent reply	other threads:[~2023-11-17 11:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 11:45 [pve-devel] [PATCH cluster/guest-common/qemu-server/container/manager v4] add backend profile support Dominik Csapak
2023-11-17 11:45 ` [pve-devel] [PATCH cluster v4 1/1] add profiles.cfg to cluster fs Dominik Csapak
2023-11-17 13:54   ` [pve-devel] applied: " Thomas Lamprecht
2023-11-17 11:45 ` Dominik Csapak [this message]
2023-11-17 11:45 ` [pve-devel] [PATCH qemu-server v4 1/3] add the VM profiles plugin Dominik Csapak
2023-11-17 11:45 ` [pve-devel] [PATCH qemu-server v4 2/3] api: add profile option to create vm api call Dominik Csapak
2023-11-17 11:45 ` [pve-devel] [PATCH qemu-server v4 3/3] qm: register and init the profiles plugins Dominik Csapak
2023-11-17 11:45 ` [pve-devel] [PATCH container v4 1/3] add the CT profiles plugin Dominik Csapak
2023-11-17 11:45 ` [pve-devel] [PATCH container v4 2/3] api: add profile option to create ct api call Dominik Csapak
2023-11-17 11:45 ` [pve-devel] [PATCH container v4 3/3] pct: register and init the profiles plugins Dominik Csapak
2023-11-17 11:45 ` [pve-devel] [PATCH manager v4 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=20231117114548.3208470-3-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal