Hi all, I was wondering if there was a neat way to override the settings file present in the devstack plugin stackforge project.
For eg: stackforge/devstack-plugin-glusterfs I plan to use `enable_plugin glusterfs <repo>` in my local to setup GlusterFS backend for openstack But I am forced to use the settings that the above repo has. Is there a way for the user setting up devstack to use plugin but specify his/her own settings file ? I guess not, and i see 2 ways of doing it - both not the best solutions tho': 1) create settings.multi-backend, settings.blah-blah etc in the stackforge project and have an optional [settings] arg to the enable_plugin which tells devstack which settings file to source 2) Create different gitref's (branches) for each version of settings file one want to support and use that gitref in the enable_plugin to clone Both of these need the plugin dev's co-operation I was hoping it would be good if there was a way for backend specific options in the settings file to be overridden by the end user, that ways he/she can use the plugin and still override the backend specific options based on the local env Thoughts ? thanx, deepak
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
