Wrong name of Cinder role in case of vCenter
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Roman Prykhodchenko | ||
5.1.x |
Won't Fix
|
High
|
Fuel Partner Integration Team | ||
6.0.x |
Fix Released
|
High
|
Roman Prykhodchenko |
Bug Description
When using vCenter as a hypervisor, it's allowed to use VMWare vCenter as a storage backend for Cinder. However, the role for Cinder is named as 'Storage - Cinder LVM' which is wrong.
-------
api: '1.0'
astute_sha: 6a11a7c481d116e
auth_required: true
build_id: 2014-10-20_00-01-06
build_number: '20'
feature_groups:
- mirantis
fuellib_sha: 598f2b7212f6865
fuelmain_sha: 598122bd61175a9
nailgun_sha: 098099ccce353eb
ostf_sha: de177931b53fbe9
production: docker
release: '6.0'
release_versions:
2014.1.1-6.0:
VERSION:
api: '1.0'
astute_sha: 6a11a7c481d116e
build_id: 2014-10-20_00-01-06
build_number: '20'
feature_
- mirantis
fuellib_sha: 598f2b7212f6865
fuelmain_sha: 598122bd61175a9
nailgun_sha: 098099ccce353eb
ostf_sha: de177931b53fbe9
production: docker
release: '6.0'
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → 6.0 |
description: | updated |
tags: | added: partner |
Changed in fuel: | |
assignee: | Fuel Partner Integration Team (fuel-partner) → Anton Zemlyanov (azemlyanov) |
Changed in fuel: | |
assignee: | Anton Zemlyanov (azemlyanov) → Fuel Partner Integration Team (fuel-partner) |
status: | Confirmed → Triaged |
tags: | added: release-notes |
Changed in fuel: | |
assignee: | Fuel Partner Integration Team (fuel-partner) → Roman Prykhodchenko (romcheg) |
status: | Triaged → In Progress |
no longer affects: | fuel/6.1.x |
Actually, this is the way how we implemented that in MOS 5.x. Cinder-volume service is running only when you assign "Storage - Cinder LVM" role to a node. So, there may be two ways to fix that:
1. Modify a UI to change a name of this role to something like "Cinder VMDK".
2. Refactor Puppet manifests to run Cinder-volume services on Controller nodes every time a user choose vCenter as a hypervisor. In this case we don't need a special role for installing Cinder.
I prefer the second approach.
Also, this behavior must be documented for 5.1.1, because I don't think it's a good idea to port this huge changes back.