From 9dff563eacb1336c12e7354a01a6b5add3250d09 Mon Sep 17 00:00:00 2001 From: John Mulligan Date: Wed, 8 Jul 2026 10:18:19 -0400 Subject: [PATCH] doc/mgr: update out of date paragraph in smb.rst We still had a part of the document saying we only support the default port. We added service colocation via custom_ports/bind_addrs a while back so the doc has been out of date. Signed-off-by: John Mulligan --- doc/mgr/smb.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/mgr/smb.rst b/doc/mgr/smb.rst index 71d9ffacb71..23cd1ca8712 100644 --- a/doc/mgr/smb.rst +++ b/doc/mgr/smb.rst @@ -1688,10 +1688,11 @@ cluster has been configured for at least one share. The ``placement`` field of the cluster resource is passed onto the orchestration layer and is used to determine on what nodes of the Ceph cluster Samba containers will be run. -At this time Samba services can only listen on port 445. Due to this -restriction only one Samba server, as part of one cluster, may run on a single -Ceph node at a time. Ensure that the placement specs on each cluster do not -overlap. +The Samba containers may run on the same hosts if, and only if, the services +use different IP addresses and/or ports. If the placement spec allows more than +one container to run on the same host, use the ``bind_addrs`` field, the +``custom_ports`` field, or some combination, in the cluster resource to ensure +that the Samba server instances do not conflict. The ``smb`` clusters are fully isolated from each other. This means that, as long as you have sufficient resources in your Ceph cluster, you can run multiple -- 2.47.3