Add VMware DataStore option to the tab 'Storage Backends ' for Cinder in wizard
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Released
|
High
|
Anton Zemlyanov | ||
| 6.0.x |
Fix Released
|
High
|
Anton Zemlyanov | ||
Bug Description
When selecting vCenter as HV, there should be available 3rd storage backend option for Cinder - VMware DataStore, which is available via Cinder VMDK driver.
In 5.1 VMware DataStore is the only backend supported for Cinder wuch vCenter HV selected.
Currently UX is confusing.
A user can select an option - Default for Cinder.
Hits say that LVM will be a backend, but actually LVM doesn't work for vCenter.
In environment settings a user should go to the Cinder configuration tab and select Cinder VMDK.
There are 2 possible fixes for this issue:
1. Add 3rd Cinder storage backend option on the wizard tab.
2. Add hint to the tab 'Storage Backends' with the following text: 'VMDK driver is a default option for vCenter. Also please change a Cinder LVM option to a Cinder VMDK option in the environment settings.'
| Igor Gajsin (igajsin) wrote | #1 |
| Changed in fuel: | |
| assignee: | nobody → Igor Gajsin (igajsin) |
| Changed in fuel: | |
| milestone: | none → 5.1 |
| tags: | added: partner |
| summary: |
- There is wrong hint in tab 'Storage Backends ' in wizard. + Add VMware DataStore option to the tab 'Storage Backends ' in wizard |
| summary: |
- Add VMware DataStore option to the tab 'Storage Backends ' in wizard + Add VMware DataStore option to the tab 'Storage Backends ' for Cinder in + wizard |
| description: | updated |
| Vitaly Kramskikh (vkramskikh) wrote | #2 |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to fuel-web (master) | #3 |
| Changed in fuel: | |
| status: | Confirmed → In Progress |
| OpenStack Infra (hudson-openstack) wrote Fix merged to fuel-web (master) | #4 |
| Changed in fuel: | |
| status: | In Progress → Fix Committed |
| no longer affects: | fuel/6.0.x |
| no longer affects: | fuel/5.1.x |
| Changed in fuel: | |
| status: | Fix Committed → Won't Fix |
| Changed in fuel: | |
| importance: | High → Medium |
| importance: | Medium → High |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to fuel-web (master) | #5 |
| Changed in fuel: | |
| status: | Won't Fix → In Progress |
| OpenStack Infra (hudson-openstack) wrote | #6 |
| OpenStack Infra (hudson-openstack) wrote Change abandoned on fuel-web (master) | #7 |
| OpenStack Infra (hudson-openstack) wrote Fix merged to fuel-web (master) | #8 |
| Changed in fuel: | |
| status: | In Progress → Fix Committed |
| okosse (okosse) wrote | #9 |
As there is HCF and option #1 requires significant rework of major part of storage-related texts as they were written for Ceph only, I suggest to go with option #2 for 5.1 and #1 for 6.0