From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 0/4] add UI support for editing metric servers
Date: Fri, 20 Nov 2020 10:50:45 +0100 [thread overview]
Message-ID: <20201120095049.15194-1-d.csapak@proxmox.com> (raw)
Adds the typical sectionconfig api entry points, as well as a basic
CRUD ui under Datacenter -> Metric Server
the next step is to adapt the documentation to no refer to editing the
config anymore, adding some more useful information, as well
as adding a onlinehelp link to the ui
Dominik Csapak (4):
Status/Plugin: fix jsonschema for MTU
Status/Plugin: add id to schema
api2/cluster: add 'metricserver' api endpoints
ui: add MetricServerView to Datacenter
PVE/API2/Cluster.pm | 7 +
PVE/API2/Makefile | 1 +
PVE/API2/MetricServerConfig.pm | 238 +++++++++++++++++
PVE/Status/Plugin.pm | 6 +-
www/manager6/Makefile | 1 +
www/manager6/dc/Config.js | 6 +
www/manager6/dc/MetricServerView.js | 397 ++++++++++++++++++++++++++++
7 files changed, 655 insertions(+), 1 deletion(-)
create mode 100644 PVE/API2/MetricServerConfig.pm
create mode 100644 www/manager6/dc/MetricServerView.js
--
2.20.1
next reply other threads:[~2020-11-20 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 9:50 Dominik Csapak [this message]
2020-11-20 9:50 ` [pve-devel] [PATCH manager 1/4] Status/Plugin: fix jsonschema for MTU Dominik Csapak
2020-11-20 13:02 ` [pve-devel] applied: " Thomas Lamprecht
2020-11-20 9:50 ` [pve-devel] [PATCH manager 2/4] Status/Plugin: add id to schema Dominik Csapak
2020-11-20 13:02 ` [pve-devel] applied: " Thomas Lamprecht
2020-11-20 9:50 ` [pve-devel] [PATCH manager 3/4] api2/cluster: add 'metricserver' api endpoints Dominik Csapak
2020-11-20 13:21 ` Thomas Lamprecht
2020-11-20 9:50 ` [pve-devel] [PATCH manager 4/4] ui: add MetricServerView to Datacenter Dominik Csapak
2020-11-20 13:32 ` 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=20201120095049.15194-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal