Bug 1497220 - Starting in pike, tripleo cannot deploy ceph pools of differing PG values
Summary: Starting in pike, tripleo cannot deploy ceph pools of differing PG values
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 12.0 (Pike)
Assignee: Giulio Fidente
QA Contact: Yogev Rabl
URL:
Whiteboard:
Depends On:
Blocks: 1476046 1516389
TreeView+ depends on / blocked
 
Reported: 2017-09-29 14:08 UTC by John Fulton
Modified: 2017-12-15 17:20 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-15 17:20:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1720373 0 None None None 2017-09-29 14:08:22 UTC
OpenStack gerrit 512274 0 None None None 2017-10-30 09:33:31 UTC

Description John Fulton 2017-09-29 14:08:22 UTC
Both ceph-ansible (default in pike) and puppet-ceph (default before pike) support defining a data structure mapping Ceph pools to be created and their respective PG sizes. For example, ceph-ansible can be passed the following and it will deploy ceph pools of differing PG values:

CephPools:
  - name: mypool
    pg_nume: 256
  - name: anotherpool
    pg_num: 64

For TripleO to take advantage of this feature the following needs to be refactored:

 https://github.com/openstack/tripleo-heat-templates/blob/master/docker/services/ceph-ansible/ceph-base.yaml#L72-L84


Note You need to log in before you can comment on or make changes to this bug.