Description of problem: OSP Director is the Red Hat strategic tool to deploy OpenStack in Production environments from version OSP7 onward. Customers prefer to use Enterprise Storage array backend for cinder. Currently there are no steps to deploy OpenStack using OSP Director and integrating with EMC storage array backend with cinder. Document all the steps to configure EMC storage backend for cinder/glance/nova via OSP Director. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Updated bz description: I tried adding cinder backend of overcloud node from undercloud by updating manifest and hieradata on undercloud node. and i was able to configure backend. But, it do not configure value of "enabled_backend" in the configuration file. Also, what I observed is, after initial deployment, if we update hieradata file with new values and rerun the deployment `openstack overcloud deploy`, the new values from hieradata do not reflect on overcloud nodes. From overcloud node, I can see older values in hieradata. as per my discussion with engineering team, currently its not to update "enabled_backend" from undercloud node. So, its bug from director component rather than doc bz.
hi Pratik, with the change at [1] you should be able to add an arbitrary backend to the list of the backends enabled in Cinder by passing its config stanza name in a list, like the following: cinder_user_enabled_backends: ["my_additional_backend_stanza_name"] can you see if that works for you? 1. https://review.openstack.org/269534