Bug 1380864

Summary:	Ceph nodes deployed by OSPd via puppet-ceph should be supported by the next OSPd version regardless of future RHSC integration
Product:	Red Hat OpenStack	Reporter:	John Fulton <johfulto>
Component:	ceph	Assignee:	John Fulton <johfulto>
Status:	CLOSED DUPLICATE	QA Contact:	Yogev Rabl <yrabl>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	12.0 (Pike)	CC:	jdurgin, jomurphy, lhh, nlevine, srevivo
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
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:	2017-03-29 14:24:43 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:
Bug Depends On:
Bug Blocks:	1413723

Description John Fulton 2016-09-30 20:14:26 UTC

There is a plan to have OSPd interface with RHSC to deploy and manage Ceph in the future. 

Suppose a user installs OSPdX, which uses puppet-ceph to configure Ceph. Suppose the user then upgrades to OSPdY, which will use an API to integrate with RHSC, which will in turn use ceph-ansible to configure Ceph. This user's upgraded OSP should still be supported. 

An Ansible playbook exists to take over management of an existing Ceph cluster that was not deployed by ceph-ansible. Since puppet-ceph uses ceph-disk, the same playbook should run without any issues.

This is a tracker bug to ensure this scenario is tested.

Comment 2 John Fulton 2017-03-29 14:24:43 UTC


*** This bug has been marked as a duplicate of bug 1432561 ***