Graduate Manila (shared filesystems) support from "experimental" status
Problem/Opportunity Statement
We put features behind the "experimental features" setting when their UX is still rough, or we expect confusion/sadness to result when people use them naively. We just finished stage 1 of OpenStack Manila support. It is currently such a feature.
We want to polish the UX of this feature such that we can graduate it to non-experimental status, i.e. so that Exosphere users will see it on Manila-enabled clouds by default.
This issue captures what we need to do to achieve that.
What would success / a fix look like?
-
Fix #969 (closed) -
Degrade for OpenStack clouds that implement Manila but not with Ceph - For now, perhaps just display an 'unsupported' message in the UI? Needs a bit of design work.
-
Perhaps expose a cloud-specific configuration option to make this a non-experimental feature?
-
Collect other things we need to do, perhaps using early JS2 team feedback from jetstream-cloud/project-mgt#174, update the checklist in this issue description accordingly.