Bug 1640182

Summary:	Certain NetApp integrations will be broken after following Upgrading Red Hat OpenStack Platform guide
Product:	Red Hat OpenStack	Reporter:	Alex Stupnikov <astupnik>
Component:	documentation	Assignee:	Laura Marsh <lmarsh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	abishop, cminkema, eharney, lmarsh, tshefi
Target Milestone:	---	Flags:	tshefi: automate_bug-
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-05 13:06:28 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:
Embargoed:

Description Alex Stupnikov 2018-10-17 13:48:28 UTC

Description of problem:

openstack-cinder-volume was containerized in RHOSP 13. As a result, it is now harder to provide additional configuration files to cinder service.

The good example of this issue is cinder with multiple NetApp backends and NFS netapp_storage_protocol. Previously, it was possible to configure such setup by pushing the following configuration to controller's extraconfig:

     cinder::config::cinder_config:

        netapp1/nfs_shares_config:
            value: /etc/cinder/nfs_shares1

        netapp2/nfs_shares_config:
            value: /etc/cinder/nfs_shares2

and by creating specified files (/etc/cinder/nfs_shares1 and /etc/cinder/nfs_shares2). AFAIK, this is the recommended and the only way to configure multiple NetApp NFS backends.

As a result, customer followed official documentation [1] and get broken environment. I would like to use this bug to ask documentation team to leave a warning about containerized cinder-volume and possible issues with custom configuration files.


[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/upgrading_red_hat_openstack_platform/

Comment 1 Alan Bishop 2018-10-31 12:37:23 UTC

For situations like this, the documentation should direct the user to take advantage of the CinderVolumeOptVolumes parameter. When upgrading to the containerized environment in OSP-13, the parameter can be used to add docker volume mounts so that any custom configuration files on the host (e.g. /etc/cinder/nfs_shares1 and /etc/cinder/nfs_shares2) can be made available to the cinder-volume service when it's running in a container.