Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2024129

Summary:	[RFE] TripleO - Deploy the ceph-nfs daemon with cephadm using the ingress related Ceph spec
Product:	Red Hat OpenStack	Reporter:	Francesco Pantano <fpantano>
Component:	tripleo-ansible	Assignee:	Francesco Pantano <fpantano>
Status:	CLOSED NEXTRELEASE	QA Contact:	Yogev Rabl <yrabl>
Severity:	high	Docs Contact:
Priority:	high
Version:	18.0 (Zed)	CC:	gcharot, gfidente
Target Milestone:	Alpha	Keywords:	FutureFeature, Triaged
Target Release:	18.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-23 14:14:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1744820, 2023309, 2068030, 2097490
Bug Blocks:	2044910

Description Francesco Pantano 2021-11-17 11:51:15 UTC

Description of problem:

TripleO now uses cephadm to bootstrap the Ceph cluster and apply the related daemons [0].
ceph-nfs is still deployed using tripleo-ansible, resulting in a cephadm unmanaged component.
Since Manila is going to adapt the ganesha driver to work in a cephadm context, TripleO can now align the existing code to deploy the ceph-nfs component and manage it via the orchestrator [1].
This bz is supposed to track the required changes in TripleO:

1. Update the ceph_mkspec library to support the ingress daemon;
2. Remove the pcs ceph-nfs and vip constraints for fresh deployments;
3. Deploy a new ingress component that uses the ceph-nfs cephadm deployed daemon as backend


[0] https://github.com/openstack/tripleo-specs/blob/master/specs/wallaby/tripleo-ceph.rst
[1] https://github.com/openstack/tripleo-specs/blob/master/specs/yoga/tripleo_ceph_manila.rst

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: