Hide Forgot
Description of problem: Per the resolution of Bug 1269990, the Puppet modules in OpenStack director need the following parameters which are available in the driver, but not in the OSP puppet modules. These should be available as options as well since the multibackend modules issue has been resolved: netapp1/reserved_percentage: value: 40 netapp1/max_oversubscription_ratio: value: 10 Version-Release number of selected component (if applicable): OSP-d 8.0 Additional info: Workaround was used from kbase 2213581 (https://access.redhat.com/solutions/2213581)
The BZ description mentions adding support for configuring two driver options, but much of the discussion is centered around multi-back end deployments. It turns out the KB article for multiple heterogeneous backends [1] already provides the means for specifying values for the reserved_percentage and max_oversubscription_ratio paramters, and is shown in the BZ description. You simply need to add snippets like this to each driver section ("netall1" in this example). netapp1/reserved_percentage: value: 40 netapp1/max_oversubscription_ratio: value: 10 This leverages TripleO's cinder::config::cinder_config ability to add arbitrary parameters to the driver settings in /etc/cinder/cinder.conf. Bryan, I'm wondering if this is sufficient, or if you're asking for dedicated TripleO parameters that can be set without resorting to the cinder::config::cinder_config technique? The dedicated parameters would be useful for single back end deployments, but you'd still need to use the cinder::config::cinder_config method when deploying multiple back ends. [1] https://access.redhat.com/solutions/2213581
Just to clarify, I need to know if the customer is looking for the parameters to be supported in THT and Puppet in a single back end deployment, or a multiple back end deployment. The distinction matters.
As per comment #4 from Alan, in OSP8 it should be possible to leverage TripleO's ability to add arbitrary parameters to the driver settings in /etc/cinder/cinder.conf via cinder::config::cinder_config This functionality is documented in [1] and [2]. 1. https://access.redhat.com/solutions/2213581 2. https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/8/html/custom_block_storage_back_end_deployment_guide/