# Install Cinder on different node **URL:** \ **Category:** SUSE OpenStack Cloud\ **Created:** [October 8, 2015, 3:16pm UTC](https://forums.suse.com/t/install-cinder-on-different-node/27502 "2015-10-08T15:16:06Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Eugen](https://avatars.discourse-cdn.com/v4/letter/e/ebca7d/32.png) [@Eugen](https://forums.suse.com/u/Eugen)\ **Post date:** [October 8, 2015, 3:16pm UTC](https://forums.suse.com/t/install-cinder-on-different-node/27502/1 "2015-10-08T15:16:06Z")
Hi, I have a Cloud 5 environment (OpenStack Juno) with 4 nodes, 1 admin (VM, SLES11), 1 control (phys. SLES11) and 2 compute nodes (both phys., SLES11 and SLES12). Now what I try to accomplish is to use a new storage node running with Cinder Kilo version because of some features that are supported there, but this storage node should not be maintained by Chef. That’s why I can’t simply add it in crowbar UI as a cinder volume. So I installed Cinder services on that new node, on control node I deleted the keystone endpoints pointing to the controller and created new endpoints for the new storage node, shutdown all Cinder services on the control node and now I am able to use that new storage node. Unfortunately, it only works for a couple of minutes, until my new endpoints are deleted and the old ones get re-created, I’m not sure yet which service is responsible for that or which config file should be modified to avoid the overwriting. When I try to deactivate the cinder barclamp in crowbar I get the error message because of the dependencies, of course. But I don’t want to deactivate/delete all barclamps, I just want to tell Chef that I don’t need [http://control\_node:8776/v1/](http://control_node:8776/v1/)… anymore but only my new endpoints. Is there a way to do that without messing everything up? I’d appreciate any help or information! Regards, Eugen ---
**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\ **Post date:** [October 14, 2015, 7:30am UTC](https://forums.suse.com/t/install-cinder-on-different-node/27502/2 "2015-10-14T07:30:18Z")
eblock, It appears that in the past few days you have not received a response to your posting. That concerns us, and has triggered this automated reply. Has your issue been resolved? If not, you might try one of the following options: - Visit [http://www.suse.com/support](http://www.suse.com/support) and search the knowledgebase and/or check all the other support options available. - You could also try posting your message again. Make sure it is posted in the correct newsgroup. ([http://forums.suse.com](http://forums.suse.com)) Be sure to read the forum FAQ about what to expect in the way of responses: [http://forums.suse.com/faq.php](http://forums.suse.com/faq.php) If this is a reply to a duplicate posting, please ignore and accept our apologies and rest assured we will issue a stern reprimand to our posting bot. Good luck! Your SUSE Forums Team [http://forums.suse.com](http://forums.suse.com) ---
**Author:** ![Eugen](https://avatars.discourse-cdn.com/v4/letter/e/ebca7d/32.png) [@Eugen](https://forums.suse.com/u/Eugen)\ **Post date:** [February 5, 2016, 1:14pm UTC](https://forums.suse.com/t/install-cinder-on-different-node/27502/3 "2016-02-05T13:14:27Z")
Update for everyone who is interested: In the meantime I switched from Juno to Liberty and was able to get it working with an external cinder-volume, although I think my problems were not related to the versions but to my missing knowledge about OpenStack 😉 The most important part is (besides the right cinder.conf and the right configuration of iSCSI targets etc.) to assign an IP address that’s in the admin network, because Chef maintains a pg\_hba.conf file that only allows access from within the admin network. This way I have a functional cinder-volume (I was able to launch an instance from that volume), but the node is not maintained by Chef, which is very important in this case. ---
**Author:** ![bmwiedemann](https://avatars.discourse-cdn.com/v4/letter/b/46a35a/32.png) [@bmwiedemann](https://forums.suse.com/u/bmwiedemann)\ **Post date:** [February 8, 2016, 11:34am UTC](https://forums.suse.com/t/install-cinder-on-different-node/27502/4 "2016-02-08T11:34:14Z")
Thank you for the follow-up. The pg\_hba.conf is likely this way for security-reasons and it is good that you got your external cinder working with it.