Bug 1132648 - [RFE] Puppet should generate ceph.conf for Controller and Compute nodes
Summary: [RFE] Puppet should generate ceph.conf for Controller and Compute nodes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rubygem-staypuft
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: z1
: Installer
Assignee: Scott Seago
QA Contact: Yogev Rabl
URL:
Whiteboard:
Depends On: 1132647 1132650
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-21 18:30 UTC by Neil Levine
Modified: 2016-04-26 20:39 UTC (History)
8 users (show)

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.
Clone Of:
: 1132650 (view as bug list)
Environment:
Last Closed: 2014-10-02 12:56:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1350 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Bug Fix Advisory 2014-10-01 17:22:34 UTC

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