Project

General

Profile

Feature #50360

Configure the IP address for Ganesha

Added by Francesco Pantano about 1 month ago. Updated 14 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm/nfs
Target version:
% Done:

0%

Source:
other
Tags:
Backport:
pacific
Reviewed:
Affected Versions:
Pull request ID:

Description

The nfs ganesha service is deployed using cephadm via the spec:

---

service_type: nfs
service_id: osp_nfs
service_name: nfs.osp_nfs
placement:
  hosts:
    - oc0-controller-0
    - oc0-controller-1
    - oc0-controller-2
spec:
  namespace: ganesha
  pool: manila_data

where the port and a few other parameters can be specified.
However, when the spec section described above is processed, this component is started on *::<port>, instead of using the cluster network or
the ip address on a specific network defined by the operator.

This is a gap compared to ceph-ansible, which is able to provide this kind of feature via [1]

[1] https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-nfs/templates/ganesha.conf.j2


Related issues

Related to CephFS - Bug #50577: cephadm ganesha config breaks backward compatibility with ceph-ansible Triaged

History

#1 Updated by Sebastian Wagner 27 days ago

  • Description updated (diff)

#2 Updated by Loïc Dachary 26 days ago

  • Target version changed from v16.2.1 to v16.2.2

#3 Updated by Patrick Donnelly 14 days ago

  • Target version changed from v16.2.2 to v17.0.0
  • Backport set to pacific

#4 Updated by Patrick Donnelly 14 days ago

  • Related to Bug #50577: cephadm ganesha config breaks backward compatibility with ceph-ansible added

Also available in: Atom PDF