[library] Cinder-volume installs on controller node

[Vladimir Kuklin]

{"build_id": "2014-06-03_00-40-36", "mirantis": "yes", "build_number": "338", "nailgun_sha": "a828d6b7610f872980d5a2113774f1cda6f6810b", "ostf_sha": "c959aa55f83fe2555cf2d382559271c7a9b17467", "fuelmain_sha": "15805b14f36fc0a896f136051a3be10fea4611d9", "astute_sha": "55df06b2e84fa5d71a1cc0e78dbccab5db29d968", "release": "4.1B", "fuellib_sha": "377f27df4cb008b400b69013dbd606e6225f5c04"}

Deploy Ubuntu + nova-network+cinder node. Controller gets cinder-volume service started, which should not happen.

[Dmitry Borodaenko (angdraug)]

The real problem is that cinder-volume service running on a controller node without cinder VG still gets scheduled by cinder-scheduler, which causes volume creation to fail. Making sure cinder-volume is stopped on controllers is a band-aid around that Cinder bug.

[Aleksandr Didenko (adidenko)]

Tested on ISO 5.1 #320:

1) Ubuntu, simple flat, 2 nodes: controller + compute
There are no cinder-volume packages or processes on nodes.

2) Ubuntu, simple flat, 3 nodes: controller + compute + cinder
cinder-volume is installed and running on cinder node only.

Controller node processes:
/usr/bin/python /usr/bin/cinder-scheduler --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-scheduler.log
/usr/bin/python /usr/bin/cinder-api --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-api.log

Cinder node processes:
/usr/bin/python /usr/bin/cinder-volume --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-volume.log

Controller packages:
cinder-api
cinder-common
cinder-scheduler
python-cinder
python-cinderclient

Cinder node packages:
cinder-common
cinder-volume
python-cinder

So there is no such problem in the current master branch.

[Andrew Woodward (xarses)]

We won't be fixing low or medium bugs for 4.1.x or 5.0.x any longer. If this needs to be addressed we need to increase priority