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 docs/manager] add pvescheduler docs, improve vzdump job gui
Date: Thu, 11 Nov 2021 12:07:01 +0100	[thread overview]
Message-ID: <20211111110709.633855-1-d.csapak@proxmox.com> (raw)

* adds the pvescheduler manpage to pve-docs (not sure about the transition
  here regarding dependcies, hope it's ok this way)
* mentions the schedules in vzdump too
* hide the id on create/edit completely (autogenerate it)
* add a 'simulate' api and gui for simulating schedules

pve-docs:

Dominik Csapak (3):
  refactor calendar events into appendix
  vzdump: change vzdump.cron to pvescheduler
  add pvescheduler docs and manpage

 calendar-events.adoc | 73 ++++++++++++++++++++++++++++++++++++++++++++
 pve-admin-guide.adoc | 18 +++++++++++
 pvescheduler.adoc    | 33 ++++++++++++++++++++
 pvesr.adoc           | 72 ++-----------------------------------------
 vzdump.adoc          |  5 ++-
 5 files changed, 130 insertions(+), 71 deletions(-)
 create mode 100644 calendar-events.adoc
 create mode 100644 pvescheduler.adoc

pve-manager:

Dominik Csapak (5):
  ui: dc/Backup: never show id input field, autogenerate id
  ui: dc/Backup: fix comment sort
  api: cluster: add jobs/schedule-analyze api call
  ui: dc/Backup: add schedule simulator button
  remove pvescheduler manpage generation

 PVE/API2/Cluster.pm                      |   5 +
 PVE/API2/Cluster/Jobs.pm                 | 107 ++++++++++++++++++++
 PVE/API2/Cluster/Makefile                |   1 +
 bin/Makefile                             |   4 -
 www/manager6/Makefile                    |   1 +
 www/manager6/dc/Backup.js                |  38 ++++----
 www/manager6/window/ScheduleSimulator.js | 118 +++++++++++++++++++++++
 7 files changed, 252 insertions(+), 22 deletions(-)
 create mode 100644 PVE/API2/Cluster/Jobs.pm
 create mode 100644 www/manager6/window/ScheduleSimulator.js

-- 
2.30.2





             reply	other threads:[~2021-11-11 11:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 11:07 Dominik Csapak [this message]
2021-11-11 11:07 ` [pve-devel] [PATCH docs 1/3] refactor calendar events into appendix Dominik Csapak
2021-11-11 17:03   ` [pve-devel] applied-series: " Thomas Lamprecht
2021-11-11 11:07 ` [pve-devel] [PATCH docs 2/3] vzdump: change vzdump.cron to pvescheduler Dominik Csapak
2021-11-11 11:07 ` [pve-devel] [PATCH docs 3/3] add pvescheduler docs and manpage Dominik Csapak
2021-11-11 11:07 ` [pve-devel] [PATCH manager 1/5] ui: dc/Backup: never show id input field, autogenerate id Dominik Csapak
2021-11-11 11:07 ` [pve-devel] [PATCH manager 2/5] ui: dc/Backup: fix comment sort Dominik Csapak
2021-11-11 11:07 ` [pve-devel] [PATCH manager 3/5] api: cluster: add jobs/schedule-analyze api call Dominik Csapak
2021-11-11 11:07 ` [pve-devel] [PATCH manager 4/5] ui: dc/Backup: add schedule simulator button Dominik Csapak
2021-11-11 11:07 ` [pve-devel] [PATCH manager 5/5] remove pvescheduler manpage generation Dominik Csapak
2021-11-11 20:04 ` [pve-devel] applied-series: [PATCH docs/manager] add pvescheduler docs, improve vzdump job gui Thomas Lamprecht

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=20211111110709.633855-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