Comment 4 for bug 1323555

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.