Project

General

Profile

Actions
Copy link

Bug #62637

open

mgr/cephadm haproxy configuration uses the host IPs for Ganesha backend

Added by Paul Cuzner 8 months ago. Updated about 1 month ago.

Status:
New
Priority:
High
Assignee:
Teoman ONAY
Category:
cephadm/services
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
Ceph - v18.0.0, Ceph - v18.1.0, Ceph - v18.1.1, Ceph - v18.1.2, Ceph - v18.1.3, Ceph - v18.2.0
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When Ganesha is deployed, it's highly likely that it will be a multihomed server. This requires haproxy to target the correct IP/interface within the "backend configuration". Testing with Reef has shown that the IPs defined within the backend are the IPs that resolve to the host which in practice would potentially place the nfs traffic on a management network. In my lab the management network is 25Gb, but I think that it is more usual for the mgmt network to be 1Gb which would be severly limiting to the potential performance of Ganesha.

The problem appears to be related to the following;

https://github.com/ceph/ceph/blob/ab521e694a4c96c82885c7a155db699a85afffe4/src/pybind/mgr/cephadm/services/ingress.py#L147

Perhaps the IP address for Ganesha should be specified in a separate field in the spec, to ensure that the backend is routed correctly?

Actions
Copy link

Also available in: Atom PDF