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 access-control/manager] add realm sync jobs
Date: Mon,  4 Apr 2022 10:54:11 +0200	[thread overview]
Message-ID: <20220404085416.1761268-1-d.csapak@proxmox.com> (raw)

with this, users now can schedule realm sync jobs, instead of manually
pressing 'sync' or configuring a cronjob for 'pveum realm sync'

this series requires my previous realm sync improvment series[0].
i could make it so that it doesn't, but this way we can safely
omit the legacy 'full' and 'purge' parameters from the beginning.

not really sure about 'domainsyncjobs' api path, but i tried to be
consistent with our remaining naming for that.
(maybe we should deprecate the 'domain' thing and use 'realm'
everywhere? that would be at least consistent with the gui)

i know i have to rebase this to where the actual perl modules land
after applying hannes previous series to move the Jobs and Plugin
modules[1], but i sent it regardless, since the code itself would not change,
so it can be reviewed right now

the access-control patch needs special care, since i try to sync
independent pve-scheduler calls across the cluster. in my tests here
it worked, but that does not mean i didn't overlook some things.

as it stands now, pve-manager depends on the new access-control

0: https://lists.proxmox.com/pipermail/pve-devel/2022-March/052319.html
1: https://lists.proxmox.com/pipermail/pve-devel/2022-March/052230.html

pve-access-control:

Dominik Csapak (1):
  add realmsync plugin for jobs and CRUD api for domainsync-jobs

 src/PVE/API2/AccessControl.pm |   6 +
 src/PVE/API2/Domainsync.pm    | 278 ++++++++++++++++++++++++++++++++++
 src/PVE/API2/Makefile         |   1 +
 src/PVE/Jobs/Makefile         |   6 +
 src/PVE/Jobs/RealmSync.pm     | 192 +++++++++++++++++++++++
 src/PVE/Makefile              |   1 +
 6 files changed, 484 insertions(+)
 create mode 100644 src/PVE/API2/Domainsync.pm
 create mode 100644 src/PVE/Jobs/Makefile
 create mode 100644 src/PVE/Jobs/RealmSync.pm

pve-manager:

Dominik Csapak (4):
  Jobs: provide id and schedule to the job
  Jobs/Plugin: remove 'vzdump' from id description
  Jobs: add RealmSync Plugin and register it
  ui: add Realm Sync panel

 PVE/Jobs.pm                     |   4 +-
 PVE/Jobs/Plugin.pm              |   2 +-
 www/manager6/Makefile           |   1 +
 www/manager6/dc/Config.js       |   7 +
 www/manager6/dc/RealmSyncJob.js | 315 ++++++++++++++++++++++++++++++++
 5 files changed, 327 insertions(+), 2 deletions(-)
 create mode 100644 www/manager6/dc/RealmSyncJob.js

-- 
2.30.2





             reply	other threads:[~2022-04-04  8:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  8:54 Dominik Csapak [this message]
2022-04-04  8:54 ` [pve-devel] [PATCH access-control 1/1] add realmsync plugin for jobs and CRUD api for domainsync-jobs Dominik Csapak
2022-11-07 17:05   ` Thomas Lamprecht
2022-11-08  8:20     ` Dominik Csapak
2022-11-08  9:24       ` Thomas Lamprecht
2022-11-08 10:36         ` Wolfgang Bumiller
2022-04-04  8:54 ` [pve-devel] [PATCH manager 1/4] Jobs: provide id and schedule to the job Dominik Csapak
2022-11-07 16:14   ` [pve-devel] applied: " Thomas Lamprecht
2022-04-04  8:54 ` [pve-devel] [PATCH manager 2/4] Jobs/Plugin: remove 'vzdump' from id description Dominik Csapak
2022-11-07 16:14   ` [pve-devel] applied: " Thomas Lamprecht
2022-04-04  8:54 ` [pve-devel] [PATCH manager 3/4] Jobs: add RealmSync Plugin and register it Dominik Csapak
2022-11-07 16:14   ` [pve-devel] applied: " Thomas Lamprecht
2022-11-07 16:15     ` Thomas Lamprecht
2022-04-04  8:54 ` [pve-devel] [PATCH manager 4/4] ui: add Realm Sync panel 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=20220404085416.1761268-1-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