Storage settings in Fuel UI

[Sergii Golovatiuk]

Fuel UI has a logical mistake in "Settings" tab. Fuel UI allows to save settings if Storage settings are not set. UI should allow to store settings when "Cinder LVM over iSCSI for volumes" or "Ceph RDB for volumes" is selected. Otherwise, user will get error when he clicks on "Deploy" button. I've attached image with error description. Here is another scenario as a sample.

User selected Ceph in Wizard, but then he realized he didn't have free nodes for Ceph. He deselects "Ceph" in Settings but doesn't select "Cinder LVM over iSCSI for volumes" as he has no clue what it means. UI allows to save settings though it's not correct and user is totally puzzled.

[Vitaly Kramskikh (vkramskikh)]

+1, these 2 checkboxes should be turned into 2 radiobuttons

[Vitaly Kramskikh (vkramskikh)]

Dmitry, what do you think? Changing this will require manifests modification as instead of checking for storge.volumes_lvm.value == true or storge.volumes_ceph.value == true you will need to check for storge.volumes.value == "lvm" or "ceph"

[Dmitry Borodaenko (angdraug)]

We originally kept the checkboxes because we were going to implement support for multiple cinder backends:
https://blueprints.launchpad.net/fuel/+spec/fuel-cinder-multi-backend

The above blueprint has Low priority so it's likely that it won't be completed in 5.1. This means that we should fix the UI now and update it later if multiple cinder backends gets done.

What I don't really like about the proposed solution is how it highlights the tight coupling between settings UI and Puppet manifests. We should nail down astute.yaml structure so that we can limit impact of UI changes like that to Nailgun. Do you think it's worth a separate blueprint?

One more thing that concerns me is that the attached screenshot has nothing to do with Cinder. Can you explain the whole chain of events from misconfiguring Cinder storage to Nailgun raising an error about Image Storage? I think there's a third problem hiding there.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/96252

[Vitaly Kramskikh (vkramskikh)]

Dmitry,

I don't really see how it is possible. I really love the how easy new settings can be added to cluster and you can choose their restrictions and their representation on UI in one place. As the only way to solve it I see creating new intermediate variables in manifests which values are determined from astute.yaml and these variable used in conditions in manifests.

[Nastya Urlapova (aurlapova)]

Guys, could you set one correct status for issue in 6.1

[OpenStack Infra (hudson-openstack)]

Change abandoned by Dmitry Borodaenko (<email address hidden>) on branch: master
Review: https://review.openstack.org/96252
Reason: Obsolete change, not relevant anymore.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/334542

[OpenStack Infra (hudson-openstack)]

Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: master
Review: https://review.openstack.org/334542
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.