Bug 1132648

Summary:	[RFE] Puppet should generate ceph.conf for Controller and Compute nodes
Product:	Red Hat OpenStack	Reporter:	Neil Levine <nlevine>
Component:	rubygem-staypuft	Assignee:	Scott Seago <sseago>
Status:	CLOSED ERRATA	QA Contact:	Yogev Rabl <yrabl>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	5.0 (RHEL 7)	CC:	aberezin, adeza, ajeain, dnavale, mburns, nlevine, sclewis, yeylon
Target Milestone:	z1	Keywords:	FutureFeature, ZStream
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ruby193-rubygem-staypuft-0.3.4-2.el6ost	Doc Type:	Enhancement
Doc Text:	With this update, Ceph is being integrated into the workflow for RHEL-OSP Installer. It is configured on the controller and compute nodes. As a result, Ceph keyring and configuration files are now generated automatically during the deployment process.	Story Points:	---
Clone Of:
Clones:	1132650 (view as bug list)		Environment:
Last Closed:	2014-10-02 12:56:31 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:	1132647, 1132650
Bug Blocks:

Description Neil Levine 2014-08-21 18:30:30 UTC

Ceph MONs will be installed on the OpenStack Controller nodes.

Foreman will be provisioning the OpenStack Controller nodes so will know their hostname/IPs.

Foreman will also be provisioning the nodes to be used as Ceph OSDs.

Puppet needs to generate a ceph.conf from a template and enter the Controller hostnames into the template for the MON list.

The ceph.conf file should also list the client keyrings also generated by Puppet.

The ceph.conf should also contain details about the front-end & back-end network interfaces for the MONs and OSD nodes.

Comment 41 Yogev Rabl 2014-09-22 09:54:30 UTC

verified in version ruby193-rubygem-staypuft-0.3.5-1.el6ost.noarch

Comment 43 Scott Lewis 2014-10-02 12:56:31 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. http://rhn.redhat.com/errata/RHBA-2014-1350.html