[pve-devel] [PATCH v2 manager 04/10] use PVE::RRD for RRD data
Fabian Grünbichler
f.gruenbichler at proxmox.com
Mon Nov 11 11:28:36 CET 2019
refactored from PVE::Cluster. same code, same semantics, different file.
Signed-off-by: Fabian Grünbichler <f.gruenbichler at proxmox.com>
---
Notes:
needs a dependency on libpve-cluster-perl, but see comment in pve-cluster
PVE/API2/Nodes.pm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/PVE/API2/Nodes.pm b/PVE/API2/Nodes.pm
index 715c8563..ddeafbef 100644
--- a/PVE/API2/Nodes.pm
+++ b/PVE/API2/Nodes.pm
@@ -48,6 +48,7 @@ use Digest::MD5;
use Digest::SHA;
use PVE::API2::Disks;
use PVE::DataCenterConfig;
+use PVE::RRD;
use JSON;
use Socket;
@@ -593,7 +594,7 @@ __PACKAGE__->register_method({
code => sub {
my ($param) = @_;
- return PVE::Cluster::create_rrd_graph(
+ return PVE::RRD::create_rrd_graph(
"pve2-node/$param->{node}", $param->{timeframe},
$param->{ds}, $param->{cf});
@@ -635,7 +636,7 @@ __PACKAGE__->register_method({
code => sub {
my ($param) = @_;
- return PVE::Cluster::create_rrd_data(
+ return PVE::RRD::create_rrd_data(
"pve2-node/$param->{node}", $param->{timeframe}, $param->{cf});
}});
--
2.20.1
More information about the pve-devel
mailing list