Ask Your Question
0

controller requires cinder backend access

asked 2018-01-29 15:23:59 -0500

cbravo gravatar image

Hello,

First of, I am using CentOS 7 with Openstack Pike installed on top. My topology is as follow:

Nova, Glance, Cinder, Keystone and Horizon installed on a Controller node which is a Virtual Machine running on ESXi. I have a compute node running the Nova service that is connected through FC to an storage. What I'm trying to do is force the users to create a volume and install the OS on that volume from an ISO loaded on glance. When I try to do that, the instance creation throws an error saying that the controller is not connected to the storage solution but I don't see why it would need to be connected, since I want the compute to use the storage (EMC VNX).

If I use an ephemeral image, the instance gets created and later on I can attach a volume from the storage. However, that is not the desire solution as I want the users to boot directly from the SAN.

Should I move the Cinder services to the compute node instead? Any explanation as to why the controller is trying to access the storage? No way I can provide access since the controller is a VM hosted on VMware itself.

Greetings,

C.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2018-01-30 03:00:31 -0500

eblock gravatar image

Hi,

the default cinder design (if you follow the install guide) is that you have your control node scheduling the jobs and communicating directly with the storage back end. You can move your cinder services to your compute node, of course, I believe I have read that a couple of times here. These are the cinder services running on my control node:

control1:~ #  rpm -qa | grep cinder
openstack-cinder-backup-10.0.7~dev1-1.2.noarch
openstack-cinder-scheduler-10.0.7~dev1-1.2.noarch
python-cinder-10.0.7~dev1-1.2.noarch
openstack-cinder-api-10.0.7~dev1-1.2.noarch
python-cinderclient-1.11.0-3.3.noarch
openstack-cinder-volume-10.0.7~dev1-1.2.noarch
openstack-cinder-10.0.7~dev1-1.2.noarch

If you install them (only the ones you need, of course) on your compute node and configure them properly, it should work, too. Hope this helps!

edit flag offensive delete link more

Comments

Thank you for the information, I think that makes sense. I will configure the cinder service to the compute node to get it to work.

cbravo gravatar imagecbravo ( 2018-01-30 21:48:56 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

3 followers

Stats

Asked: 2018-01-29 15:23:59 -0500

Seen: 63 times

Last updated: Jan 30 '18