Bug 1305264

Summary:	Expand a ceph cluster from installer API
Product:	Red Hat Storage Console	Reporter:	Christina Meno <gmeno>
Component:	ceph-installer	Assignee:	Andrew Schoen <aschoen>
Status:	CLOSED ERRATA	QA Contact:	Rachana Patel <racpatel>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2	CC:	ceph-eng-bugs, ceph-qe-bugs, flucifre, hnallurv, icolle, kdreyer, mkudlej, nthomas, sankarshan
Target Milestone:	---
Target Release:	2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-installer-1.0.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 19:46:44 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:

Description Christina Meno 2016-02-06 14:26:11 UTC

Description of problem:

Ceph cluster expansion:

adding Node with roles

Configure Osds for disks in an existing OSD Node
Expectation: OSD packages are installed

Journal size should also be taken care here, when a node or OSDs are getting added

API defined here https://github.com/ceph/mariner-installer/#apiosdconfigure

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Christina Meno 2016-02-06 14:28:28 UTC

Dusmant what does "Ceph cluster expansion: adding Node with roles" mean in this context?

Comment 4 Mike McCune 2016-03-28 22:16:42 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 12 Rachana Patel 2016-08-07 15:16:13 UTC

verified with

ceph-ansible-1.0.5-23.el7scon.noarch
ceph-installer-1.0.12-3.el7scon.noarch


- able to add new MON node
- able to add new OSD node and OSDs to existing cluster
working as expected hence moving to verified

Comment 14 errata-xmlrpc 2016-08-23 19:46:44 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2016:1754