[pve-devel] [PATCH manager v2] ceph: Allow specifying cluster network separately

Philip Abernethy p.abernethy at proxmox.com
Mon Sep 4 12:34:28 CEST 2017


We always recommend putting ceph-internal communication into a separate
cluster network. Now pveceph init allows specifying a separate cluster
network. The prior behaviour is retained, so -network sets both
networks and -cluster_network overrides the cluster network if it is
set.
---
Removed needless punctuation.
 PVE/API2/Ceph.pm | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/PVE/API2/Ceph.pm b/PVE/API2/Ceph.pm
index 7f709f55..a67d3445 100644
--- a/PVE/API2/Ceph.pm
+++ b/PVE/API2/Ceph.pm
@@ -788,6 +788,12 @@ __PACKAGE__->register_method ({
 		optional => 1,
 		maxLength => 128,
 	    },
+	    cluster_network => {
+		description => "Use specific network for all internal ceph traffic",
+		type => 'string', format => 'CIDR',
+		optional => 1,
+		maxLength => 128,
+	    },
 	    size => {
 		description => 'Targeted number of replicas per object',
 		type => 'integer',
@@ -879,6 +885,10 @@ __PACKAGE__->register_method ({
 	    $cfg->{global}->{'cluster network'} = $param->{network};
 	}
 
+	if ($param->{cluster_network}) {
+	    $cfg->{global}->{'cluster network'} = $param->{cluster_network};
+	}
+
 	PVE::CephTools::write_ceph_config($cfg);
 
 	PVE::CephTools::setup_pve_symlinks();
-- 
2.11.0





More information about the pve-devel mailing list