| Summary: | [RFE] OSP director puppet modules need additional NetApp driver options | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Bryan Yount <byount> |
| Component: | RFEs | Assignee: | Alan Bishop <abishop> |
| Status: | CLOSED NOTABUG | QA Contact: | Tzach Shefi <tshefi> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 (Liberty) | CC: | abishop, asoni, byount, dabrown, dhill, eharney, geguileo, gfidente, ipilcher, markmc, mburns, nobody+akarlsso, pgrist, scohen, srevivo |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged, ZStream |
| Target Release: | 8.0 (Liberty) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-12 18:34:30 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: | |
|
Description
Bryan Yount
2016-12-01 05:35:07 UTC
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/ |