Bug 1380864 - Ceph nodes deployed by OSPd via puppet-ceph should be supported by the next OSPd version regardless of future RHSC integration
Summary: Ceph nodes deployed by OSPd via puppet-ceph should be supported by the next O...
Keywords:
Status: CLOSED DUPLICATE of bug 1432561
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: ceph
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: John Fulton
QA Contact: Yogev Rabl
URL:
Whiteboard:
Depends On:
Blocks: 1413723
TreeView+ depends on / blocked
 
Reported: 2016-09-30 20:14 UTC by John Fulton
Modified: 2017-03-29 14:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-29 14:24:43 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.