This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

It should be possible to provide arbitary config params for ceph by passing the following via environment file:

parameter_defaults:
  ExtraConfig:
    ceph_classes:
      - ceph::confg
    ceph::config:
      DEFAULT/my_ceph_parameter:
        value: my_value
      DEFAULT/another_parameter:
        value: another_value

which should result in ceph.conf being populated with something like:

[DEFAULT]
my_ceph_parameter: my_value
another_parameter: another_value

This isn't working for me. Here is what I added to an environment file that is part of our solution:

parameter_defaults:
  ExtraConfig:
    ceph_classes:
      - ceph::conf
    ceph::conf:
      global/max_open_files:
        value: 131072

Note: Deployments failed until I determined the proper ceph_classes name is "ceph::conf" (not "ceph::confg" or "ceph::config").

The overcloud deployment succeeds, but no additional entry appears in ceph.conf. The hiera data appears to be correct:

[heat-admin@overcloud-cephstorage-0 ~]$ sudo hiera ceph_classes
["ceph::conf"]
[heat-admin@overcloud-cephstorage-0 ~]$ sudo hiera ceph::conf
{"global/max_open_files"=>{"value"=>131072}}

I expected to find a "max_open_files" entry in the [global] section of ceph.conf, but there isn't one.

hi Alan, please excuse me but the syntax I suggested in comment #4 is indeed wrong; if I remember correctly we wrote it down together during a session at the summit but I didn't test it. My bad.

The correct syntax is:

parameter_defaults:
  ExtraConfig:
    ceph_classes:
      - ceph::conf
    ceph::conf::args:
      DEFAULT/my_ceph_parameter:
        value: my_value
      DEFAULT/another_parameter:
        value: another_value

which in your use case ( comment #6 ) would become:

parameter_defaults:
  ExtraConfig:
    ceph_classes:
      - ceph::conf
    ceph::conf:args:
      global/max_open_files:
        value: 131072

I tested it this time and it works as intended.

As a side note, with OSP8 templates we also don't need to pass ::conf as an additional class (in ceph_classes) because it's included by default so one could remove:

    ceph_classes:
      - ceph::conf

(In reply to Alan Bishop from comment #5)
> This isn't working for me. Here is what I added to an environment file that
> is part of our solution:
> 
> parameter_defaults:
>   ExtraConfig:
>     ceph_classes:
>       - ceph::conf
>     ceph::conf:
>       global/max_open_files:
>         value: 131072

this should be:

parameter_defaults:
  ExtraConfig:
    ceph_classes:
      - ceph::conf
    ceph::conf::args:
      global/max_open_files:
        value: 131072

Giulio, I confirmed the corrected syntax you provided works as you describe. Thanks!

On one hand, this RFE is not needed because the capability already exists. On the other hand, I have not seen any documentation that explains how to use the capability.

I recommend adding a write-up to an appropriate section in the Red Hat OpenStack Platform Partner Integration guide (https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/partner-integration/partner-integration).

Alan, I am adding some docs in tripleo.org to document this feature [1].

Do you think we can move the BZ to docs and do something similar with the official RH OSP documentation?

1. https://review.openstack.org/#/c/323464/

That sounds like a good idea to me.

Since the feature exists, and this is now a docs bug, I'm changing the flags back to rhos-9.0? to match the Target Release "9.0 (Mitaka)"

*** Bug 1319328 has been marked as a duplicate of this bug. ***

It looks like this BZ fell through the cracks.

There's a page for this content here:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/9/html/red_hat_ceph_storage_for_the_overcloud/creation#Configuring_Ceph_Storage_Cluster_Settings

Same content appears on OSP10 and OSP11 branches.

@Giulio, is there anything further we need for this content?

thanks Dan, I think the example in the link you posted is fine, Alan do you think it is sufficient? Maybe we can close this as CURRENTRELEASE?

I reviewed the documentation at the link Dan provided, and feel it does a very good job of explaining things. I agree this BZ can be closed.

Thanks, guys!