[UX] vCenter requires NSX or DVS driver but it's not in core
Bug #1541613 reported by
Andrew Woodward
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Anton Zemlyanov | ||
8.0.x |
Fix Released
|
Critical
|
Anton Zemlyanov |
Bug Description
In order to enable the vCenter Hyper-visor selection, the mouse over says we need the network provider to be DVS or NSX
Moving on to the networking (next page), there is no DVS or NSX backend to select
expected result, information on the hyper-visor page must clearly identify that vCenter can not be enabled with out a plugin for DVS/NSX. If possible a link to where to find the plugin should be included.
This is considered UX critical
Changed in fuel: | |
assignee: | nobody → Anton Zemlyanov (azemlyanov) |
tags: | added: area-pce-vcenter |
To post a comment you must log in.
If there is sufficient time/bandwidth to update the Puppet manifests to default to KVM acceleration and fall back to QEMU systematically, we should implement this code and make both the wizard and the Settings page show a KVM/QEMU checkbox to be in parity.
If there is not sufficient time to do the full solution, revert the UI to individual radio buttons for KVM and QEMU so that both wizard and settings has the same UX and we will modify the implementation to the above solution in the following release.