Description of problem: I greatly appreciate packstack adding the support to configure glusterfs as a backend to cinder. One feature to enhance it would be to allow options to be specified. I work around this by issuing this command, since the one option I care about is backupvolfile-server. ssh ${CONFIG_CINDER_HOST} "sed 's/^172.31.143.91:\\/OSTACKcinder\$/172.31.143.91:\\/OSTACKcinder -o backupvolfile-server=172.31.143.92/' /etc/cinder/shares.conf" Version-Release number of selected component (if applicable): [root@cvd1 site-packages]# yum list installed | grep packstack This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. openstack-packstack.noarch 2013.2.1-0.9.dev840.el6ost [root@cvd1 site-packages]# How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
My understanding is Packstack's scope is all-in-one deployment type, even though it can handle few other scenarios. If that is confirmed then this RFE is not going to be honored and foreman deployment should be used. Effectively there is no much need for glusterfs storage in such case, well besides testing but that's not user driven.
Steve, Would it be okay to drop this from Packstack? The target of simplifying Packstack is to make it maintainable. If we keep implementing things like this we will never make it happen.