[pve-devel] [PATCH cluster v2 6/8] remove now unused old corosync ringX_addr formats

Thomas Lamprecht t.lamprecht at proxmox.com
Tue Jun 11 19:36:31 CEST 2019


no users of this anymore, so drop it.

Signed-off-by: Thomas Lamprecht <t.lamprecht at proxmox.com>
---

NO changes v1 (RFC) -> v2

 data/PVE/API2/ClusterConfig.pm | 16 ----------------
 1 file changed, 16 deletions(-)

diff --git a/data/PVE/API2/ClusterConfig.pm b/data/PVE/API2/ClusterConfig.pm
index 9c91880..dabdeb4 100644
--- a/data/PVE/API2/ClusterConfig.pm
+++ b/data/PVE/API2/ClusterConfig.pm
@@ -18,22 +18,6 @@ my $clusterconf = "/etc/pve/corosync.conf";
 my $authfile = "/etc/corosync/authkey";
 my $local_cluster_lock = "/var/lock/pvecm.lock";
 
-my $ring0_desc = {
-    type => 'string', format => 'address',
-    description => "Hostname (or IP) of the corosync ring0 address of this node.",
-    default => "Hostname of the node",
-    optional => 1,
-};
-PVE::JSONSchema::register_standard_option("corosync-ring0-addr", $ring0_desc);
-
-my $ring1_desc = {
-    type => 'string', format => 'address',
-    description => "Hostname (or IP) of the corosync ring1 address of this node.".
-	" Requires a valid configured ring 1 (bindnet1_addr) in the cluster.",
-    optional => 1,
-};
-PVE::JSONSchema::register_standard_option("corosync-ring1-addr", $ring1_desc);
-
 my $nodeid_desc = {
     type => 'integer',
     description => "Node id for this node.",
-- 
2.20.1





More information about the pve-devel mailing list