826f6850d0
1) ceph-nfs (ganesha-ceph) - use NFSv4 only This is recommended upstream. v3 and UDP require portmapper (aka rpcbind) which we do not want, except where Ubuntu ganesha version (2.6) forces it by requiring enabled UDP, see [1]. The issue has been fixed in 2.8, included in CentOS. Additionally disable v3 helper protocols and kerberos to avoid meaningless warnings. 2) ceph-nfs (ganesha-ceph) - do not export host dbus It is not in use. This avoids the temptation to try handling it on host. 3) Properly handle ceph services deploy and upgrade Upgrade runs deploy. The order has been corrected - nfs goes after mds. Additionally upgrade takes care of rgw for keystone (for swift emulation). 4) Enhance ceph keyring module with error detection Now it does not blindly try to create a keyring after any failure. This used to hide real issue. 5) Retry ceph admin keyring update until cluster works Reordering deployment caused issue with ceph cluster not being fully operational before taking actions on it. 6) CI: Remove osd df from collected logs as it may hang CI Hangs are caused by healthy MON and no healthy MGR. A descriptive note is left in its place. 7) CI: Add 5s timeout to ceph informational commands This decreases the timeout from the default 300s. [1] https://review.opendev.org/669315 Change-Id: I1cf0ad10b80552f503898e723f0c4bd00a38f143 Signed-off-by: Radosław Piliszek <radoslaw.piliszek@gmail.com>
38 lines
462 B
Django/Jinja
38 lines
462 B
Django/Jinja
NFS_CORE_PARAM {
|
|
Protocols = 4;
|
|
Enable_NLM = false;
|
|
Enable_RQUOTA = false;
|
|
Enable_UDP = false;
|
|
}
|
|
|
|
NFS_KRB5 {
|
|
Active_krb5 = false;
|
|
}
|
|
|
|
EXPORT
|
|
{
|
|
Export_id=1;
|
|
|
|
Path = "/";
|
|
|
|
Pseudo = /cephfs;
|
|
|
|
Access_Type = RW;
|
|
|
|
Protocols = 4;
|
|
|
|
Transports = TCP;
|
|
|
|
FSAL {
|
|
Name = CEPH;
|
|
}
|
|
}
|
|
|
|
LOG {
|
|
Facility {
|
|
name = FILE;
|
|
destination = "/var/log/kolla/ceph/ceph-nfs.log";
|
|
enable = active;
|
|
}
|
|
}
|