Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

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!