Skip to content

Commit 9804349

Browse files
committed
Swap to rgw port 8100, with justification
1 parent 0aaed81 commit 9804349

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

doc/source/configuration/cephadm.rst

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -319,7 +319,10 @@ RGWs are defined with the following:
319319
- id: myrgw
320320
count_per_host: 1
321321
spec:
322-
rgw_frontend_port: 80
322+
rgw_frontend_port: 8100
323+
324+
The port chosen must not conflict with any other processes running on the Ceph
325+
hosts. Port 8100 does not conflict with our default suite of services.
323326

324327
Ceph RGWs require additional configuration to:
325328

@@ -382,10 +385,11 @@ RGWs with hyper-converged Ceph
382385
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
383386

384387
If you are using a hyper-converged Ceph setup (i.e. your OpenStack controllers
385-
and Ceph storage nodes share the same hosts), you will need to change the
386-
``rgw_frontend_port``. This is because port 80 (and 443) will be bound to the
387-
Kolla-deployed haproxy. You should choose a custom port that does not conflict
388-
with any OpenStack endpoints (``openstack endpoint list``), such as port 8100.
388+
and Ceph storage nodes share the same hosts), you should double-check that
389+
``rgw_frontend_port`` does not conflict with any processes on the controllers.
390+
For example, port 80 (and 443) will be bound to the Kolla-deployed haproxy. You
391+
should choose a custom port that does not conflict with any OpenStack endpoints
392+
too (``openstack endpoint list``).
389393

390394
You may also want to use the Kolla-deployed haproxy to load balance your RGWs.
391395
This means you will not need to define any Ceph ingress services. Instead, you

0 commit comments

Comments
 (0)