There is "Enable Cinder" checkbox on the VMware tab in Fuel UI. It mean
that this vCenter should be used as backend for cinder-vmware. But in
Fuel 6.1 only one vCenter accessed and special checkbox totally useless
Therefore I offer very simple logik: if you want have cinder with vmdk
backend, assign cinder-vmware role to any node. Do nothing in opposite
case.
Reviewed: https:/ /review. openstack. org/169830 /git.openstack. org/cgit/ stackforge/ fuel-web/ commit/ ?id=264a5c94e7a a236c1c8f188efc fdd261682d0b7a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 264a5c94e7aa236 c1c8f188efcfdd2 61682d0b7a
Author: Igor Gajsin <email address hidden>
Date: Wed Apr 1 19:02:38 2015 +0300
remove enable-cinder checkobox
There is "Enable Cinder" checkbox on the VMware tab in Fuel UI. It mean
that this vCenter should be used as backend for cinder-vmware. But in
Fuel 6.1 only one vCenter accessed and special checkbox totally useless
Therefore I offer very simple logik: if you want have cinder with vmdk
backend, assign cinder-vmware role to any node. Do nothing in opposite
case.
Change-Id: I35d01f892a2807 5cdd37ac684d68c fc89b40a41e
Implements: blueprint cinder-vmdk-role
Closes-bug: 1435725